How veerachandra2008/pheonix-main works
Phoenix is an esports tournament platform for players, organizers, and administrators. Players browse tournaments, register, pay or verify passes, and follow results; organizers manage tournaments, rosters, attendance, and leaderboards, while admins oversee platform operations. The Next.js application uses both a Flask API and Supabase-backed routes/data access. README-documented player, team, live-broadcast, and admin capabilities are represented, though sampled source does not establish all their runtime connections.
Main entry points: app.py Flask API · organizer Organizer Portal · tournaments-db.ts Tournament Data Access · tournaments.py Tournament API
Components 29
Player Experience
- Tournament Hub
src/app/tournaments/page.tsx - Tournament Detail
src/app/tournaments/[slug]/page.tsx - Registration Flow
src/app/registration/[slug]/page.tsx - Pass Verification
src/app/verify/page.tsx - Player and Team Hubs
src/app/players - Live Broadcast
src/components/xenova/LiveTelecaster.tsx - Leaderboards
src/app/leaderboards/page.tsx - Teams and Games
src/app/teams
Tournament Operations
- Organizer Portal
src/app/organizer - Admin Portal
src/app/admin
Application APIs
- Flask API
backend/app.py - Tournament API
backend/routes/tournaments.py - Payments API
backend/routes/payments.py - Registration API
backend/routes/registrations.py - Authentication API
backend/routes/auth.py - Organizer Applications
backend/routes/applications.py - Attendance and Rosters
backend/routes/attendance.py - Leaderboard API
backend/routes/leaderboard.py - Next API Routes
src/app/api/[...path]/route.ts
Identity and Data
- Tournament Data Access
src/lib/tournaments-db.ts - Flask API Client
src/lib/flask-api.ts - Session Manager
src/lib/auth-session.ts - Supabase Client
src/lib/supabase.ts - Supabase Data Store
- Backend Configuration
backend/config.py - API Cache
backend/cache.py - QR Scanner Engine
src/lib/qr-scanner-engine.ts - QR Decoder Fallback
src/lib/qr-decoder-fallback.ts
Other components
- Players
Connections 41
- Players → Tournament Hub: browses
README.md - Players → Tournament Detail: views
README.md - Players → Registration Flow: registers through
README.md - Players → Pass Verification: verifies pass
README.md - Tournament Hub → Tournament Data Access: loads tournaments
src/app/tournaments/page.tsx - Tournament Detail → Tournament Data Access: loads tournament data
src/app/tournaments/[slug]/page.tsx - Tournament Detail → Flask API Client: requests API data
src/app/tournaments/[slug]/page.tsx - Registration Flow → Payments API: submits payment
- Pass Verification → Flask API Client: checks passes
src/app/verify/page.tsx - Pass Verification → QR Scanner Engine: scans codes
src/app/verify/page.tsx - QR Scanner Engine → QR Decoder Fallback: decodes with
src/lib/qr-scanner-engine.ts - Players → Player and Team Hubs: explores profiles
README.md - Players → Live Broadcast: watches matches
README.md - Players → Leaderboards: checks rankings
README.md - Players → Teams and Games: explores teams
README.md - Players → Organizer Portal: applies to host
README.md - Organizer Portal → Organizer Applications: submits application
- Organizer Portal → Tournament API: manages tournaments
- Organizer Portal → Attendance and Rosters: manages attendance
- Organizer Portal → Leaderboard API: manages results
- Admin Portal → Organizer Applications: reviews applications
- Flask API → Tournament API: registers blueprint
backend/app.py - Flask API → Payments API: registers blueprint
backend/app.py - Flask API → Registration API: registers blueprint
backend/app.py - Flask API → Authentication API: registers blueprint
backend/app.py - Flask API → Organizer Applications: registers blueprint
backend/app.py - Flask API → Attendance and Rosters: registers blueprints
backend/app.py - Flask API → Leaderboard API: registers blueprint
backend/app.py - Tournament Data Access → Supabase Client: queries
src/lib/tournaments-db.ts - Tournament Data Access → Session Manager: reads session
src/lib/tournaments-db.ts - Tournament Data Access → Flask API Client: requests API
src/lib/tournaments-db.ts - Supabase Client → Supabase Data Store: connects to
- Next API Routes → Supabase Client: queries
src/app/api/[...path]/route.ts - Next API Routes → Supabase Data Store: reads and writes
src/app/api/[...path]/route.ts - Flask API → Backend Configuration: loads configuration
backend/app.py - Tournament API → API Cache: uses cache
backend/routes/tournaments.py - Authentication API → API Cache: uses cache
backend/routes/auth.py - Tournament API → Backend Configuration: uses Supabase client
backend/routes/tournaments.py - Organizer Applications → Authentication API: reads user state
backend/routes/applications.py - Organizer Applications → Tournament API: reads tournament state
backend/routes/applications.py - Payments API → Backend Configuration: uses configuration
backend/routes/payments.py