How essamdev47/course-registration-v2 works
This is a course-registration web application: applicants submit course and personal details, administrators review registrations and approve, reject, or delete them, and email notifications report application events. The browser clients call a FastAPI backend, which validates and processes requests using SQLAlchemy-backed registration records. A service worker provides caching for an offline-oriented web experience. The source excerpts show the API-to-model, database, and email dependencies; the HTML pages and deployment configuration were not sampled, so their wiring is not inferred.
Main entry points: main.py API Routes · database.py Database Session · models.py Registration Model · email_utils.py Email Sender
Components 13
Browser Clients
- Registration Form
register.html - Form Submission
register.js - Admin Dashboard
admin.html - Review Actions
admin.js - Offline Cache
sw.js
Registration API
- API Routes
main.py
Registration Data
- Registration Model
models.py - Database Session
database.py - SQLite Store
Notifications
- Email Sender
email_utils.py
Other components
- Applicant
- Administrator
- SMTP Email
Connections 11
- Applicant → Registration Form: opens
- Form Submission → API Routes: submits
register.js - Administrator → Admin Dashboard: uses
- Review Actions → API Routes: requests actions
admin.js - API Routes → Registration Model: queries and updates
main.py - API Routes → Database Session: creates sessions
main.py - Registration Model → Database Session: uses base
models.py - Database Session → SQLite Store: connects to
database.py - API Routes → Email Sender: sends notices
main.py - Email Sender → SMTP Email: sends via SMTP
email_utils.py - Offline Cache → Applicant: serves cached pages