How andreypividori/polytechtours-padelstarterkit works
Project type and purpose
• This is a full-stack web application "Corpo Padel" for managing corporate padel tournaments.
• Tech stack:
• Backend: FastAPI with JWT auth, SQLAlchemy/SQLite, Pytest tests
• Frontend: Vue 3 + Vue Router + Pinia, Axios client, Tailwind CSS, Cypress E2E
Key high-level components
• User’s Browser (UI)
• Frontend Application (Vue)
• Components, Views, Router, Pinia store, Axios service
• Backend Application (FastAPI)
• API layer (auth endpoints, dependency injection)
• Core (configuration, security/jwt, hashing, brute-force lockout)
• Models (SQLAlchemy ORM)
• Schemas (Pydantic)
• Database connector (SQLite)
• Persistent Store: SQLite file
• External/Internal services
• JWT issuer/validator (built into backend)
• Environment/config service (.env files)
• Test suites (unit tests + E2E) – optional to include as side-components
Relationships and data-flow
• Browser → Frontend (served via Vite dev server or static hosting)
• Frontend → Backend: HTTPS requests via Axios interceptors, sending JWT in headers
• Backend → Database: SQLAlchemy sessions read/write to SQLite file
• Backend (Security module) ↔ JWT tokens (create/verify)
• Frontend store (Pinia) persists auth state and routes guard navigation
Architectural patterns & design principles
• Clear separation of concerns:
• Presentation (Vue components + router guards)
• State management (Pinia)
• Service layer (Axios wrapper with interceptors)
• API layer / business logic (FastAPI routers, dependency injection)
• Data access (SQLAlchemy models + database module)
• Layered architecture in backend:
• API → core services → data access → persistence
• Token-based stateless authentication (JWT)
• Configuration via environment variables (.env)