TANAY API hosts automations, Discord bots, and an admin interface for operations across everything SoDA does. If Notion handles our knowledge, TANAY API operationalizes it.

</aside>

Source code

Admin interface

The TANAY API is designed as a modular monolith (as opposed to a microservice-based architecture) for simplicity of maintenance and deployment. Modules encapsulate logic and functionality in such a way that different responsibilities are separated. Modules are a first-class feature of Flask, so components and services can easily be swapped in/out without affecting each other.

Architecture

architecture-beta
    group api(cloud)[TANAY API]

    service db(database)[SQL DB] in api
    service vps(server)[VPS] in api
    service ui(internet)[Admin UI] in api

    vps:R --> L:db
    ui:R --> L:vps
    
    service frontend(internet)[Frontend]
    
    frontend:B --> T:vps

module information

Calendar module design

backups

hostinger handles periodic backups for us 🙂 [put a link here]

make sure we still do backups if we switch off hostinger.

how to add a new module to codebase

Create a module folder in modules using mkdir modules/<module_name>,
If the API requires REST capabilities create an api.py for it and if it renders webpages, create a views.py in the modules folder.,
If you require any shared resources within the app (such as .env secret), before importing it look in shared.py (preventing circular imports), if it will be needed in multiple modules, import it to shared.py first instead of importing it directly.,