How cumulusclad-developer/edtech-platform-django- works
Project type and purpose
• This is a Django-and-DRF monolithic backend API for an educational platform (“EdTech Platform”).
• It exposes REST endpoints for users, assessments, curricula, billing, current affairs, gamification, push notifications, OAuth, sessions, audit & activity tracking, etc.
• It supports JWT auth, OpenAPI docs (Swagger/Redoc), push via Firebase Cloud Messaging, Redis caching, and security hardening.
File structure
Top-level folders & files:
• edtech_platform/ ← Django project settings, ASGI/WSGI, URL routing
• manage.py, .env, .env.example, requirements.txt
• apps/ (monorepo style – each app is a Django “bounded context”):
– accounts, api, assessments, audit, billing, current_affairs, curriculum, devices, gamification, notifications_app, oauth_app, sessions_app, useractivity_tracking
• core/ ← shared filters & utilities
• migrations/tests/serializers/views in each app
• api/auth_views.py, api/health_views.py, api/urls.py handle global auth & health endpoints
• devices/fcm_service.py and notifications_app/push_api.py encapsulate FCM integration
README for additional insights
• Services: PostgreSQL (via DATABASE_URL), Redis (cache, session backend, brute-force lockouts), Firebase for push
• Auth: JWT with short access, rotating refresh, blacklist
• Docs: OpenAPI schema + SwaggerUI/Redoc
• Security: HTTPS, HSTS, secure cookies, CSP, CORS, django-axes, throttling