How inspedralbes/tr1-type-racer-royale-grup3daw works
Project type and purpose
• This is a full-stack, real-time multiplayer game platform built with a Vue.js SPA in the frontend and a Node.js/Express API in the backend. It supports user authentication, room creation/joining, live game sessions via WebSockets, score tracking, and stats.
File structure
• Top-level:
• .github/ – CI/CD workflows (deploy.yml)
• docker-compose.dev.yml, docker-compose.prod.yml – multi-container configs
• nginx.Dockerfile, nginx.conf – reverse proxy / static server
• backend/ – Express app, REST controllers, socket manager, Sequelize (SQL) models & migrations, optional Mongo connection, middleware, state manager
• frontend/vue-project/ – Vue 3 app scaffolded with Vite, Pinia stores, Vue Router, single-file components, communication manager for HTTP & sockets
• doc/ – API docs, dev credentials, images
• The backend is organized around controllers & routes, with a clear MVC-style separation of concerns. A stateManager holds in-memory game state; Sequelize handles RDBMS persistence; mongo.js suggests an additional NoSQL store.
Essential details to capture
• Nginx as reverse proxy and static file host
• Vue SPA communicating via both HTTP(S) and WebSocket
• Express controllers versus Socket Manager handling different traffic
• StateManager’s role in persisting transient game state
• Dual persistence layers: SQL for users/scores/info, MongoDB for flexible or ephemeral data
• CI/CD integration with GitHub Actions and Docker Compose deployment