How 2305100-vineet/competition-platform works
Arenafy is a full-stack tournament platform for cricket, football, and PUBG. Organizers create tournaments, open registration, approve team entries, then generate fixtures or brackets (or PUBG match days); match results are normalized by discipline-specific processors and feed standings or knockout advancement. Players browse tournaments and register teams, while organizers manage lifecycle and results. The graph includes the client, API routing, domain controllers, sport processors, and persistence models. Some subsystem links rely on README descriptions or the source index because their implementation excerpts were not supplied.
Main entry points: app.js HTTP application · TournamentDetail.jsx Tournament workspace · registration.controller.js Team registration · match.controller.js Fixtures and results
Components 27
Web client
- Web application
client/src/App.jsx - Session context
client/src/context/AuthContext.jsx - API client
client/src/api/client.js - Tournament workspace
client/src/pages/TournamentDetail.jsx - Result form
client/src/components/SubmitResultForm.jsx - Bracket display
client/src/components/Bracket.jsx
API and identity
- HTTP application
server/src/app.js - Authentication routes
server/src/routes/auth.routes.js - Match routes
server/src/routes/match.routes.js - Tournament routes
server/src/routes/tournament.routes.js - Registration routes
server/src/routes/registration.routes.js - JWT guard
server/src/middleware/auth.middleware.js
Tournament operations
- Account and reset
server/src/controllers/auth.controller.js - Tournament lifecycle
server/src/controllers/tournament.controller.js - Team registration
server/src/controllers/registration.controller.js - Fixtures and results
server/src/controllers/match.controller.js - Processor registry
server/src/discipline/registry.js - Cricket results
server/src/discipline/cricket/cricket.resultProcessor.js - Football results
server/src/discipline/football/football.resultProcessor.js - PUBG results
server/src/discipline/pubg/pubg.resultProcessor.js
Persistence and integrations
- User records
server/src/models/User.js - Tournament records
server/src/models/Tournament.js - Registration records
server/src/models/Registration.js - Team and roster
server/src/models/Team.js - Match records
server/src/models/Match.js - Email delivery
server/src/utils/mailer.js
Other components
- Players and organizers
Connections 28
- Players and organizers → Web application: uses
client/src/App.jsx - Web application → Session context: provides session
client/src/App.jsx - Web application → Tournament workspace: routes to
client/src/App.jsx - Session context → API client: requests auth
client/src/context/AuthContext.jsx - Tournament workspace → API client: loads and updates
client/src/pages/TournamentDetail.jsx - Tournament workspace → Result form: renders
client/src/pages/TournamentDetail.jsx - Tournament workspace → Bracket display: renders
client/src/pages/TournamentDetail.jsx - HTTP application → Authentication routes: mounts
server/src/app.js - HTTP application → Match routes: mounts
server/src/app.js - HTTP application → Tournament routes: mounts
server/src/app.js - HTTP application → Registration routes: mounts
server/src/app.js - Authentication routes → Account and reset: dispatches
server/src/routes/auth.routes.js - Match routes → JWT guard: guards mutations
server/src/routes/match.routes.js - Match routes → Fixtures and results: dispatches
server/src/routes/match.routes.js - Tournament routes → JWT guard: guards mutations
server/src/routes/tournament.routes.js - Tournament routes → Tournament lifecycle: dispatches
server/src/routes/tournament.routes.js - Registration routes → Team registration: dispatches
server/src/routes/registration.routes.js - Account and reset → User records: reads and writes
server/src/controllers/auth.controller.js - Account and reset → Email delivery: sends email
server/src/controllers/auth.controller.js - Team registration → Registration records: creates and reads
server/src/controllers/registration.controller.js - Team registration → Tournament records: updates participants
server/src/controllers/registration.controller.js - Team registration → Team and roster: checks roster
server/src/controllers/registration.controller.js - Fixtures and results → Match records: creates and queries
server/src/controllers/match.controller.js - Fixtures and results → Tournament records: reads and updates
server/src/controllers/match.controller.js - Fixtures and results → Processor registry: looks up processor
server/src/controllers/match.controller.js - Processor registry → Cricket results: selects
server/src/discipline/registry.js - Processor registry → Football results: selects
server/src/discipline/registry.js - Processor registry → PUBG results: selects
server/src/discipline/registry.js