How ulwus/fu-examination-system works
• Frontend: Represent the static assets (Bootstrap, Chart.js, Vanilla JS, Ace Editor) and templates that form the user interface for students and educators.
• Backend: Highlight the Django framework, including key modules:
• Core project (FUExaminationSystem) with global settings, routing (urls.py), and interface endpoints.
• Individual Django apps: “exams”, “competitions”, “dashboard”, “ide”, “users”, and “datasets”. Each app encapsulates its own models, views, forms, and templates.
• Real-time Communication: Include Django Channels (in the “ide” module) for websocket-based communication.
• Database and Storage: Represent MongoDB as the primary database for user and exam data, and Redis as both the cache and message broker.
• External Services and Infrastructure: Include external components such as the web server (Gunicorn), Docker as the containerization environment, and Docker Compose orchestrating the containers.
• Error Handling and Logging: Although not a separate service, note that custom error pages and Django Logging are part of the system’s resilience and monitoring.
Relationships and Data Flow
• Centralized Routing: Illustrate how URLs (defined in the core urls.py and those in each app’s urls.py) route requests to the appropriate Django views.
• Database and Cache Interactions: Connect the backend to MongoDB (for persistent data) and to Redis (for caching & message brokering).
• Docker Environment: Enclose the backend, Celery worker, and ancillary services in a container (or a set of containers) as defined in the Dockerfile and docker-compose.yml. This highlights the deployment and isolation of services.