How dcaybe/web_nckh9 works
Project type and purpose
• This is a full-stack Django web application (“web_nckh9” project + “app_nckh9” app) that provides:
– Multi-role interfaces (admin, teacher, student) with HTML/CSS/JS frontends
– RESTful/DRF APIs (“api_views.py”, serializers)
– Background processing (Celery tasks)
– An embedded AI chatbot service (under app_nckh9/kaira_chatbot)
– File uploads/media management and static asset delivery
File structure
• Top-level:
– manage.py, web_nckh9/ (settings, wsgi, asgi), app_nckh9/ (Django app)
– staticfiles/ & media/uploads/ (collected assets, user uploads)
– db.sqlite3 (development DB), redis.log, celery.py, tasks.py
• app_nckh9/:
– api_views.py, serializers.py → API layer
– views.py, templates/, static/js & static/css → frontend rendering
– migrations/ → schema migrations (SQLite or Postgres in prod)
– celery.py, tasks.py → Celery worker definitions
– kaira_chatbot/ → embedded chatbot: vector store (FAISS), embedding & LLM caches, model binaries, chat routing (main.py)
• External integrations:
– Redis as Celery broker & cache (redis.log)
– Potential third-party LLM API or local model files
README/architecture.md
• No content provided, but conventions like architecture.md indicate intention to document modules & flows
• Rely on file names and folder structure to reconstruct component interactions