How ayushi544/event-management works
Main Components
• Frontend: HTML/CSS templates for creating, viewing, and managing events.
• Backend: Flask application logic (found in both app.py for SQL and json_app.py for JSON).
• Data Layer:
• SQL Version: MySQL database (as indicated by the “events sql” folder).
• JSON Version: Files like event_data.json and CSV files (in "event json" and "static/attachments").
• External Services: Google Meet link validation and file upload features.
Relationships and Data Flow
• For the SQL version: Show how the Flask app interacts with the MySQL database and serves HTML pages.
• For the JSON version: Illustrate how the Flask app reads and writes JSON data and CSVs.
• User interactions (create event, view event list) flowing from the frontend to the backend and then to the database or file system.
Architectural Patterns
• MVC-like pattern: Separate templates (view), Flask routes (controller), and data (model via SQL or JSON).
• Maintain a clear separation between the two data handling strategies by indicating two separate pathways (one for MySQL, one for JSON).
Technology Stack
• Python with Flask for the web framework.
• MySQL as the primary database (for the SQL version) and JSON/CSV files for the alternate version.
• HTML, CSS, and optionally Bootstrap for the UI.
• Git for version control.