How prasanthcoder/seating-arrangement-and-invigilator-scheduling works
Main Components
• Web Server/Django Application: Represent the umbrella system with its Django project under the “epics” directory (for settings, URLs, WSGI, ASGI) and two Django apps (“facsch” and “seating”).
• Frontend/UI Layer: Include the templates (HTML files such as admindash.html, faculty.html, etc.) and static assets (CSS under “static”) that define the user interfaces for admin, faculty, and possibly students.
• Database: Mark PostgreSQL as the central data store for user data, exam seating, invigilator schedules, ticket records, and any other persistent data.
• Background Task Processing: Illustrate the Celery worker (configured in epics/celery.py), which handles asynchronous tasks such as scheduled email notifications via SMTP.
• External Messaging/AMQP: Include a connection to the CloudAMQP server (as indicated in the README) that’s tied to Celery.
• Email Service (SMTP): Show the email service used to dispatch notifications for exam schedules and invigilator reminders.
Relationships and Interactions
• Frontend (browser clients) interacts with the Django server for login, form submissions (faculty ticket raising, seating or scheduling info upload).
• The Django server talks directly to the PostgreSQL database for CRUD operations across the different modules.
• Upon receiving input (such as excel uploads or scheduling form submissions), the Django apps (seating and facsch) process the information according to business rules (like seating constraints or invigilator work hour constraints).
• For actions that require asynchronous processing (email notifications, scheduling computations), Django enqueues tasks to Celery.
• Celery workers grab tasks from the AMQP message queue (CloudAMQP) and execute these jobs.
• After processing, results (e.g., generated seating arrangement Excel) are sent back to the client via a HTTP response or made available for download.
Architectural Patterns and Principles
• The project is organized as a typical Django MVC (Model-View-Controller) pattern.
• There is a clear separation between concerns: Data management (Django models within seating and facsch), presentation (templates), request routing (urls.py in multiple apps), and asynchronous processing (Celery).
• Integration of external systems (SMTP, CloudAMQP, Excel file inputs/outputs) which form peripheral but vital components in the overall architecture.
Relevant Technologies and Their Roles
• Django: Core web framework managing web requests, rendering UI, and model logic.
• Celery + CloudAMQP: Handling asynchronous tasks (ex. sending emails as per schedule).
• PostgreSQL: Primary database for persistent storage.
• SMTP: Used for sending email notifications.
• Excel Files: Both as input (data ingestion) and output (result generation).