How routinetinc/routinet-server works
Project type and purpose
• This is a monolithic Django-based backend service (no dedicated frontend in this repo).
• The README only covers coding/git conventions; architectural intent comes from the file tree.
• It exposes RESTful endpoints via multiple Django apps: feed, routine, run, supply_auth.
File structure
• Top-level Django project:
• KGAvengers/ – project settings, ASGI/WSGI entrypoints, middleware.
• manage.py – Django management utility.
• requirements.txt – Python dependencies.
• drop_and_create_db.py – DB setup script.
• Apps (each under root):
• feed/ – feed-related REST views, models, admin, migrations, caching, graph-DB utility code.
• routine/ – task scheduling endpoints, serializers, custom view packages.
• run/ – execution endpoints, management commands (graph_db), models, views.
• supply_auth/ – authentication/authorization, custom user models, views.
• Utilities:
• feed/utils/graph_db/* – abstractions and connections to a graph database.
• feed/cache.py – caching layer (likely Redis or similar).
• routine/utils and run/management/commands – helper scripts.
README for additional insights
• We infer use of Python 3.11, Django’s MVT, and a relational DB (via migrations) plus a graph DB.