How piyush0924/game works
Project type and purpose
• This is a full-stack, real-time online gaming platform.
• Frontend: React.js SPA (built with Vite) serving game dashboards, community pages, and embedded minigames.
• Backend: Node.js + Express REST API + Socket.IO for real-time move updates.
• Database: MongoDB storing users, posts, game sessions.
File structure
• Top-level “Backend” folder:
• server.js – entry point
• config/db.js – MongoDB connection setup
• models/ – Mongoose schemas (User, Game, Post)
• routes/ – Express routes for game, post, user
• Frontend assets in project root:
• public/ – static HTML (legacy mini-games), media (videos, images), standalone tic-tac-toe
• src/ – React components, pages, assets, application logic
• vite.config.js, tailwind.config.js – build & styling config
• Shared:
• package.json & lockfiles at root and Backend
README for additional insights
• Confirms tech stack: React + Socket.IO client on front, Express + Socket.IO server at back.
• Describes REST endpoints (GET /api/games, POST /api/games).
• Real-time events: ‘move’ emit and ‘updateMove’ receive.
Main components and relationships
a. Components to include:
• Client (React SPA)
• Static-file server (Express static middleware serving /public)
• REST API (Express routes)
• Real-time layer (Socket.IO server & client)
• Database (MongoDB)
• Third-party services (e.g. MongoDB Atlas or local instance)
b. Interactions:
• React UI → HTTP REST → Express routes → Mongoose → MongoDB
• React UI ↔ WebSocket (Socket.IO) → Express server ↔ WebSocket → React UIs (broadcast moves)
• Express static middleware → serves public assets (index.html, game HTML, JS, CSS)
c. Architectural patterns:
• 3-tier architecture: Presentation (React), Application (Express controllers), Data (MongoDB)
• MVC-style backend: models (Mongoose), controllers (routes), views (static files)
• Event-driven real-time updates via Socket.IO
d. Key technologies:
• Frontend: React.js, Vite, Tailwind CSS, Socket.IO client
• Backend: Node.js, Express.js, Socket.IO server, Mongoose
• Database: MongoDB (local or Atlas)
Detail without over-fragmenting
• Real-time vs. REST flows separately.