How digeesh038/esports-points-table-maker works
This is an esports tournament management product: organizers create tournaments and stages, enroll teams and players, record match results, and publish standings; payments and live updates support that workflow. The frontend routes users through public and protected pages and calls the backend API. The backend routes requests through authentication and domain controllers, which use scoring/leaderboard services and persistent models. The tree documents additional organization, dashboard, and payment capabilities. Some controller and page implementations were not sampled, so those feature links are documented only where the route wiring or explicit source references support them.
Main entry points: app.js HTTP application · index.js Domain models · matchController.js Match operations · leaderboardService.js Leaderboard service
Components 21
Web application
- Tournament UI
esports-tournament-frontend/src/App.jsx - Session context
esports-tournament-frontend/src/contexts/AuthContext.jsx - Live connection
esports-tournament-frontend/src/contexts/SocketContext.jsx - Team management
esports-tournament-frontend/src/pages/TeamsPage.jsx - Tournament pages
esports-tournament-frontend/src/pages/TournamentDetailPage.jsx - Standings pages
esports-tournament-frontend/src/pages/LeaderboardPage.jsx - API client
esports-tournament-frontend/src/api/client.js
API and access
- HTTP application
esports-tournament-backend/src/app.js - Authentication
esports-tournament-backend/src/middlewares/authMiddleware.js
Competition operations
- Tournament stages
esports-tournament-backend/src/controllers/tournamentController.js - Teams and rosters
esports-tournament-backend/src/controllers/teamController.js - Match operations
esports-tournament-backend/src/controllers/matchController.js - Payments
esports-tournament-backend/src/controllers/paymentController.js
Scoring and standings
- Scoring engine
esports-tournament-backend/src/services/scoringEngine.js - Leaderboard service
esports-tournament-backend/src/services/leaderboardService.js - WebSocket service
esports-tournament-backend/src/services/websocketService.js
State and integrations
- Domain models
esports-tournament-backend/src/models/index.js - PostgreSQL
esports-tournament-backend/src/config/database.js - Redis cache
esports-tournament-backend/src/config/redis.js
Other components
- Organizer or player
- Razorpay
Connections 27
- Organizer or player → Tournament UI: uses
esports-tournament-frontend/src/App.jsx - Tournament UI → Session context: provides session
esports-tournament-frontend/src/App.jsx - Tournament UI → Live connection: provides live state
esports-tournament-frontend/src/App.jsx - Team management → API client: requests teams
- Tournament pages → API client: requests tournaments
esports-tournament-frontend/src/pages/TournamentDetailPage.jsx - Standings pages → API client: requests standings
- API client → HTTP application: HTTP requests
- HTTP application → Tournament stages: routes tournaments
esports-tournament-backend/src/app.js - HTTP application → Teams and rosters: routes teams
esports-tournament-backend/src/app.js - HTTP application → Match operations: routes matches
esports-tournament-backend/src/app.js - HTTP application → Payments: routes payments
esports-tournament-backend/src/app.js - Authentication → Domain models: loads user
esports-tournament-backend/src/middlewares/authMiddleware.js - Tournament stages → Scoring engine: gets ruleset
esports-tournament-backend/src/controllers/tournamentController.js - Tournament stages → Redis cache: clears cache
esports-tournament-backend/src/controllers/tournamentController.js - Teams and rosters → Domain models: creates teams
esports-tournament-backend/src/controllers/teamController.js - Teams and rosters → Redis cache: invalidates standings
esports-tournament-backend/src/controllers/teamController.js - Match operations → Scoring engine: submits results
esports-tournament-backend/src/controllers/matchController.js - Match operations → WebSocket service: publishes updates
esports-tournament-backend/src/controllers/matchController.js - Match operations → Redis cache: uses cache
esports-tournament-backend/src/controllers/matchController.js - Payments → Razorpay: processes payments
- Scoring engine → Domain models: stores results
esports-tournament-backend/src/services/scoringEngine.js - Scoring engine → Leaderboard service: updates standings
esports-tournament-backend/src/services/scoringEngine.js - Leaderboard service → Domain models: reads competition data
esports-tournament-backend/src/services/leaderboardService.js - Leaderboard service → Redis cache: uses cache
esports-tournament-backend/src/services/leaderboardService.js - Leaderboard service → WebSocket service: publishes standings
esports-tournament-backend/src/services/leaderboardService.js - Domain models → PostgreSQL: uses Sequelize
esports-tournament-backend/src/models/index.js - Live connection → WebSocket service: receives live events