How gelerom/champmaster works
ChampMaster is a championship-management application: users register racers, results can be read from an image, and the product calculates points and displays standings. The graph preserves those documented stages alongside championship, team, organization, and account-management capabilities visible in the tree. The excerpts show frontend routing and authentication state, image-analysis modules, and PostgreSQL access; many route and feature implementations were not sampled, so uncertain connections are left out or marked unverified.
Main entry points: axiosConfig.jsx API client · db_connection.py Database connection · api.py Application API · db_vysledky_pg.py Race results
Components 22
Web application
- Web routes
frontend/src/App.jsx - User context
frontend/src/context/UserContext.jsx - API client
frontend/src/api/axiosConfig.jsx - Championship manager
frontend/src/pages/SampionatManagerPage.jsx - Team manager
frontend/src/pages/TeamManagerPage/TeamManagerPage.jsx - Organization manager
frontend/src/pages/RoleManagerPage.jsx
Championship services
- Application API
app/routes/api.py - Analysis endpoint
app/routes/analysis.py - Image analysis
app/logic/analyza_obrazu/main.py - OCR engine
app/logic/analyza_obrazu/ocr.py - Points and standings
app/logic/pozice_vysledkove_tabulky.py - Championship scheduler
app/logic/championship_scheduler.py
Identity and access
- Authentication routes
app/routes/auth/login_logout.py - Auth services
app/my_auth/auth_helpers.py - Email delivery
app/my_auth/email_service.py
Persistence
- Database connection
app/data/db_connection.py - Championship data
app/data/db_sampionaty_pg.py - Driver data
app/data/db_jezdci_pg.py - Team data
app/data/db_tymy_pg.py - Race results
app/data/db_vysledky_pg.py - PostgreSQL
Other components
- Racer or manager
Connections 25
- Racer or manager → Web routes: uses
- Web routes → User context: provides context
frontend/src/App.jsx - User context → API client: requests data
frontend/src/context/UserContext.jsx - Championship manager → API client: sends requests
- Team manager → API client: sends requests
frontend/src/pages/TeamManagerPage/TeamManagerPage.jsx - Organization manager → API client: sends requests
frontend/src/pages/RoleManagerPage.jsx - API client → Application API: calls API
- Application API → Championship data: accesses
- Application API → Driver data: accesses
- Application API → Team data: accesses
- Racer or manager → Analysis endpoint: submits result image
- Analysis endpoint → Image analysis: invokes analysis
- Image analysis → OCR engine: performs OCR
app/logic/analyza_obrazu/main.py - Image analysis → Race results: loads race data
- Racer or manager → Points and standings: views points and standings
- Championship scheduler → Championship data: updates statuses
- Authentication routes → Auth services: uses auth services
- Auth services → Email delivery: sends verification mail
- Championship data → Database connection: opens connection
app/data/db_sampionaty_pg.py - Driver data → Database connection: opens connection
app/data/db_jezdci_pg.py - Team data → Database connection: opens connection
app/data/db_tymy_pg.py - Race results → Database connection: opens connection
app/data/db_vysledky_pg.py - Database connection → PostgreSQL: connects to
app/data/db_connection.py - Driver data → Race results: queries results
app/data/db_jezdci_pg.py - Race results → Championship data: queries championship
app/data/db_vysledky_pg.py