How trevbook/pax-pal-2025 works
Project type and purpose
• It consists of:
• A React-based frontend (Vite build, served by Nginx).
• A Python backend (likely FastAPI or Flask given main.py, models.py, db.py) with Docker support.
• A database (used by the backend, set up via docker-compose).
• Data-exploration/ETL experiments in Jupyter notebooks (under experiments/).
• CI/CD pipelines (GitHub Actions, Cloud Run templates).
File structure
• Top-level:
• .github/ (CI/CD definitions, Cloud Run service templates)
• docker-compose.yml (local dev orchestration)
• backend/ (Python API, Dockerfile, models, utilities)
• frontend/ (React code, Dockerfile, Nginx config)
• experiments/ (notebooks for data scraping & prepping)
• Patterns: clear separation of concerns – frontend, backend, data-prep.
• Configs: GitHub workflows for building/pushing images; Cloud Run for deployments.
README for additional insights
• The README simply describes the goal: an exploratory webapp for games at PAX East 2025.
Detail
• Break each major service into subcomponents if needed (e.g., show Nginx ↔ static files ↔ SPA build artifacts).
• Ports (e.g., 80/443 for frontend, 8000 for backend).
• Environment differences (local via docker-compose vs. cloud via Cloud Run).