How kpe-chaiwat/gamelottery works
Primusgame is a browser-based multi-game player/reward application backed by a Go Fiber API and MongoDB. The user workflow is to open a game, submit a play or round, and receive results; the backend routes requests through handlers into game services that read or update player and reward records. The frontend also exposes a home page, result view, and reset page. No README or frontend/API-call source was provided, so frontend-to-API wiring and several unsampled backend handler/service relationships are not asserted.
Main entry points: App.jsx Page router · main.go API server · mongo.go MongoDB · game1_postUpdate_handler.go Game 1 handler
Components 32
Web application
- Page router
primusgame/src/App.jsx - Home
primusgame/src/pages/Home.jsx - Game 1 UI
primusgame/src/pages/game1.jsx - Game 2 UI
primusgame/src/pages/game2.jsx - Game 3 UI
primusgame/src/pages/game3.jsx - Game 4 UI
primusgame/src/pages/game4.jsx - Victor result
primusgame/src/pages/VictorResult .jsx - Reset page
primusgame/src/pages/ResetGame.jsx - Game 1 API
primusgame/src/api/api_game1.js - Game 2 API
primusgame/src/api/api_game2.js - Game 3 API
primusgame/src/api/api_game3.js - Game 4 API
primusgame/src/api/api_game4.js - Conclude API
primusgame/src/api/api_conclude.js - Reset API
primusgame/src/api/resetAPI.js
HTTP API
- API server
primusgame-backend/main.go - Game 1 routes
primusgame-backend/routes/game1_routes.go - Game 3 routes
primusgame-backend/routes/game3_routes.go - Game 4 routes
primusgame-backend/routes/game4_routes.go - Game 1 handler
primusgame-backend/handlers/game1_postUpdate_handler.go - Game 3 handler
primusgame-backend/handlers/game3_handler.go - Game 4 handler
primusgame-backend/handlers/game4_handler.go - Game 2 routes
primusgame-backend/routes/game2_routes.go - Game 2 handler
primusgame-backend/handlers/game2_handler.go - Result handling
primusgame-backend/routes/result_route.go - Reset handling
primusgame-backend/routes/reset.go
Game services
- Game 1 rewards
primusgame-backend/services/game1_reward_service.go - Game 3 matching
primusgame-backend/services/game3_service.go - Game 4 rounds
primusgame-backend/services/game4_service.go - Game 2 logic
primusgame-backend/services/game2_service.go - Player operations
primusgame-backend/services/player_service.go
Persistence
- MongoDB
primusgame-backend/config/mongo.go
Other components
- Player
Connections 25
- Player → Page router: opens pages
- Page router → Home: routes to
- Page router → Game 1 UI: routes to
- Page router → Game 2 UI: routes to
- Page router → Game 3 UI: routes to
- Page router → Game 4 UI: routes to
- Page router → Victor result: routes to
- Page router → Reset page: routes to
- API server → Game 1 routes: mounts routes
- API server → Game 2 routes: mounts routes
- API server → Game 3 routes: mounts routes
- API server → Game 4 routes: mounts routes
- API server → Result handling: mounts routes
- API server → Reset handling: mounts routes
- Game 1 routes → Game 1 handler: dispatches
- Game 3 routes → Game 3 handler: dispatches
- Game 4 routes → Game 4 handler: dispatches
- Game 1 handler → Player operations: finds player
- Game 1 handler → Game 1 rewards: updates reward
- Game 3 handler → Game 3 matching: matches and updates
- Game 4 handler → Game 4 rounds: processes rounds
- Game 1 rewards → MongoDB: reads and writes
- Game 3 matching → MongoDB: reads and writes
- Game 4 rounds → MongoDB: reads and writes
- Player operations → MongoDB: reads players