How creepymemes/barbermanager works
Project Type & Purpose
• Full-stack, containerized web application for barber shop management
• Frontend: React (Vite) SPA served by Nginx
• Backend: Django REST API served by Gunicorn
• Asynchronous tasks via Celery + Redis
• Persistent data in Postgres
• Reverse proxy (Nginx) for HTTPS termination & routing
Break Down the File Structure into High-Level Components
• Root: Docker Compose definitions (docker-compose.dev.yml, docker-compose.prod.yml), deploy scripts
• frontend/: Dockerfiles (dev/prod), Nginx config, Vite config, React source (src/)
• backend/: Django project (config/, api/), Celery config, migrations, Dockerfiles, manage.py, tasks.py
• Shared infra: .env, GitHub Actions (CI/CD), docs/
Core Components
A. User Agent
– Browser or Mobile Client (HTTP/HTTPS)
B. Reverse Proxy
– Nginx container (nginx.conf at project root) routing to frontend Nginx or Gunicorn
C. Frontend Infrastructure
1. Builder Stage (Vite)
2. Nginx Server Stage serving the compiled React SPA
D. Backend Infrastructure
1. Gunicorn WSGI server
2. Django REST API
3. Django settings split (dev/prod)
E. Asynchronous Processing
1. Celery Worker (api/tasks.py, config/celery.py)
2. Celery-Beat scheduler
F. Datastores & Brokers
1. Postgres database
2. Redis (as Celery broker & cache if used)
G. External Services
– SMTP Email provider (EMAIL_HOST, etc. from .env)
H. CI/CD & Deploy
– GitHub Actions workflows (test.yml, deploy.yml)
– deploy.sh script
Relationships & Data Flows
• User → HTTPS → Reverse Proxy
• Reverse Proxy →
– “/static/*” → Frontend Nginx → React SPA
– “/api/*” → Gunicorn → Django REST views
• Django ORM → Postgres (reads/writes)
• API endpoints trigger Celery tasks → Redis
• Celery Worker pulls tasks from Redis → executes business logic → writes to Postgres (e.g., send reminder emails)
• Celery-Beat → scheduled tasks → enqueues into Redis
• Django can also enqueue tasks for Celery Worker or Beat
Architectural Patterns & Design Principles
• Containerization: one container per “service” (frontend, backend, celery, beat, db, redis)
• Single-page Application (SPA) consuming REST API
• 12-factor app: configuration via environment variables, separate build/runtime stages
• Layer separation: presentation (React), application/API (Django), data (Postgres), queue (Redis/Celery)
• Dev vs Prod Dockerfiles and Compose files for environment parity
Diagramming Recommendations
• Client → Reverse Proxy → Services
• API → DB / Queue
• Queue → Worker → DB / Email
• Green for networking (Nginx, reverse proxy)
• Blue for frontend (Vite, React)
• Dark blue or grey for backend (Gunicorn, Django)
• Orange for message queue (Redis, Celery)
• Purple for data store (Postgres)
– Optionally include port mappings and environment variable references for clarity