How pseudo-lab/event-bingo works
Project type and purpose
• This is a full-stack web application for running a Bingo game and a community board.
• The “backend” folder contains a Python FastAPI app (routes, services, Pydantic schemas, SQLAlchemy models, Alembic migrations), handling authentication (JWT + social login), bingo logic, and board/comment CRUD.
• The “frontend” folder contains a Vite + React + TypeScript app, organized into feature modules (Bingo, Builder, Community, Runner, Admin), offering UIs for playing Bingo, viewing/editing boards, and user flows.
• Dockerfiles and docker-compose.yaml orchestrate the backend, frontend, and a MySQL database.
File structure
• Top level:
• docker-compose.yaml → orchestrates 3 containers: frontend, backend, MySQL DB
• backend/ → Python app, Dockerfile, pyproject.toml, MySQL startup script
• frontend/ → React app, Dockerfile, package.json, Vite config
• backend/app/api/… → domain-specific route modules (auth, bingo, board), each with routes.py, schema.py, services/*.
• backend/app/models/… → ORM models.
• backend/app/core/… → DB setup, dependency injection, logging.
• backend/app/migrations/… → Alembic environment and version scripts.
• frontend/src/modules/… → feature folders, each with components and screens.
• frontend/src/api/*.ts → client wrappers for backend endpoints.
README for additional insights
• No content provided; architecture must be inferred from structure and naming conventions.
Elements
• Between Browser and React UI (user actions & rendering)
• Between React UI and API endpoints (/api/auth, /api/bingo, /api/board)
• Between Backend and DB (ORM queries)
• Between Backend and OAuth provider
• Blue rectangles for client-side components
• Green rectangles for server-side components
• Grey hexagon for external services (Discord)
• Annotations for key data flows: login→JWT, fetch boards, post comments, play bingo.