How codingnoob1224/qbeep_final works
Project type and purpose
• QBeep is a Django-based monolithic web application for event registration, check-in/out, feedback collection, and admin analytics.
• Key use cases: user signup/login, event creation & listing, QR-code-based attendance, form-based feedback, and dashboard analytics.
File structure
• Top‐level Django project folder:
• project/ (ASGI, WSGI, settings, URLs)
• apps: events/, feedback/, member/
• templates/ + static/ + media/
• manage.py, requirements.txt, Zeabur deployment YAML
• Each app follows Django’s MVT: models.py (DB schema), views.py (request handlers), urls.py (routing), templates/ (UI), migrations/ (schema history).
• Configuration & deployment: settings.py defines DB, installed apps, middleware; zeabur.yaml for cloud deploy.
README for additional insights
• Tech Stack: Python 3.12, Django 5.1.1, SQLite (or MySQL), Bootstrap 5, QRCode library, Zeabur.
• Features: role-based access, QR code generation (Base64) for check-in, visual analytics dashboards.
Main components & their interactions
a. User Interface Layer (Frontend)
• Templates + Bootstrap CSS + JavaScript
• URL entry points: registration pages, event pages, feedback forms, dashboards
b. Application Layer (Django Backend)
• member app: user auth, profiles, QR generation
• events app: event CRUD, registration tracking, QR validation
• feedback app: questionnaire rendering, response storage, analytics
• project (global settings, middleware, URL dispatcher)
c. Data Layer
• SQLite database (models persisted across all apps)
• media/ storage for uploaded files and generated QR codes
d. External & Deployment
• Zeabur cloud platform for CI/CD and hosting
• Optional external database (MySQL) or email/SMS gateways for password reset by phone
Architectural patterns & design principles
• Monolithic Django MVT: separation of concerns among models, views, templates
• Modular apps: each feature domain (member, events, feedback) in isolated Django apps
• Role-based access control: Django permissions and decorators
• Stateless HTTP API for check-in/out (could evolve into microservices)
• Base64 QR code generation as an internal utility (events.utils or member.utils)