How thetatau/cmt works
Main components
• Client / Browser – represents the end users accessing the web application.
• Web Application (Backend) – a Django application broken into modular apps:
• thetatauCMT (handles the core chapter management functionalities, including chapters, ballots, events, finances, forms, submissions, surveys, tasks, notes, etc.)
• anonymizer and core – provide supporting functionality.
• OpenEdX (integration module) and others.
• Database – typically PostgreSQL managed in a container as suggested by configuration in the .envs and compose/production/postgres.
• Async Task Processor – include a celery worker component (the project shows a taskapp module and tasks folder).
• Static and Template Assets – while served by Django in many cases, clearly delineate the frontend components handled via the templates, static files (CSS, JS, images) and SASS compilation.
• Deployment/Infrastructure – represent Docker containers (with docker-compose for local and production), as well as environment-specific configurations (compose/local vs. compose/production).
Relationships and interactions
• Connection between Django and the celery worker, which processes asynchronous tasks (such as background emails, notifications, and maintenance commands).
• Static file serving (for CSS, JS, images) over the network or via a CDN if that feature is used in production.
• Integration of third-party services or any external dependency like email services, if relevant from configuration and testing instructions.
Architectural patterns
• Modular design of the Django project – distinct apps (organized under thetatauCMT, core, anonymizer, etc.) each handling specific business logic.
• Point out the separation of development environments using Docker Compose with different configurations for local vs. production.
• Reverse proxy (Traefik) as an external edge service that manages routing and TLS termination.
• Use of environment-specific settings (with the config/settings directory containing base, local, production, etc.) which enforce a layered configuration model.
Specify relevant technologies and frameworks
• Django (with Cookiecutter Django as the starter) as the web framework.
• PostgreSQL for the database.
• Docker/Docker Compose for containerization and deployment.
• Traefik as the reverse proxy.
• Celery (with thetatauCMT/taskapp/celery) for asynchronous task processing.
• Sass and live reload tooling for the frontend styling (as noted in the README’s live-reloading section).