How gentbajko/reports-system works
Main Components
a) Web Layer:
• Frontend (Templates Layer)
• HTML templates structure (calendar, log, project, task, user sections)
• It's using a templating engine (likely Jinja2 based on the structure)
b) Application Layer:
• Controllers Layer
• Calendar, Dashboard, Log, Project, Task, and User controllers
• Views Layer
• Separate view handlers for different entities
• Dependencies
• Authentication
• Database session management
c) Core Domain Layer:
• Core Models
• User, Project, Task, Log, Calendar entities
• Enums
• Permissions and Task Status
d) Data Access Layer:
• Database Adapters
• MySQL implementation
• Repositories
• Entity-specific repositories
• Models/Mappers
• ORM mappings for each entity
• Session Management
• SQLAlchemy session handling
e) Infrastructure:
• MySQL Database
• Alembic Migrations
• Email Service (indicated by email templates)
[Web Browser] → [Templates Layer]
• ↓
[Controllers Layer] ← → [Views Layer]
• ↓
[Core Domain Layer (Models & Enums)]
• ↓
[Data Access Layer (Repositories & Mappers)]
• ↓
[Database (MySQL)]
Important Relationships
• Authentication flow through the dependencies
• How the email service integrates with the system
• Database migration path using Alembic
Technical Details
• Python 3.12 runtime
• FastAPI/ASGI server (implied by the structure)
• SQLAlchemy ORM
• Alembic migrations
• Jinja2 templating
• MySQL database
• UV package management
Deployment Components
• Docker container for MySQL
• Application server
• Environment configuration