How shronal/khec_ems works
Project type and purpose
• This is a full-stack web application built with Django (Python) for Khwopa Engineering College’s Event Management System.
• Purpose: allow administrators to create/manage events, enable users (students/faculty) to browse and register, and plan future notification and analytics features.
File structure
• Top-level:
• manage.py – Django CLI entry point
• db.sqlite3 – development database
• requirements.txt – Python dependencies
• ems/ – core project configuration (settings, URLs, ASGI/WSGI)
• ems_app/ – “events” app (models, views, forms, URLs, migrations)
• users/ – custom user management app (models, views, forms, URLs, migrations)
• templates/ – HTML templates (admin, base, events, users)
• static/ – CSS, images
• Patterns: Django’s MVT (Model-View-Template)
• Config/Deployment: settings.py contains database, middleware, apps; wsgi/asgi for deployment.
Extract README insights
• Tech stack: Django, Bootstrap, PostgreSQL (prod), SQLite (dev)
• Future components: Notification System, Analytics Dashboard
• Role-based access: Admin vs. Student/Faculty
Main components
a. Client (Browser)
– UI layers: login/register pages, event list/detail, admin dashboards
b. Web Server (Django)
– ems/settings.py & URLs
– ems_app (Event logic: models.py, views.py, forms.py)
– users app (Auth logic: models.py, views.py, forms.py)
– Templates (HTML + Bootstrap) & Static files (CSS/JS/images)
c. Database
– PostgreSQL (prod) or SQLite (dev) storing User, Event, Registration, Feedback, Category tables
d. Admin Interface
– Django Admin (automatically registered via admin.py in both apps)
e. (Planned) External Services
– Notification service (email/SMS)
– Analytics service or module
Relationships and interactions
• Browser ↔ Django server over HTTP/HTTPS
• Django Views ↔ Templates (render HTML)
• Views ↔ Forms (input validation)
• Views ↔ Models (ORM queries to DB)
• Admin user interacts with Django Admin UI ↔ ORM ↔ DB
• Future: Django signals or Celery tasks → Notification service
• Future: Data aggregation → Analytics module or external BI tool
Architectural patterns/design principles
• Django’s MVT: clear separation of data (Models), logic (Views), and presentation (Templates)
• Role-based access control via decorators or middleware
• Modular apps (ems_app, users) for separation of concerns
• DRY: shared base.html, static folder