How ygstudio-game/cinesync works
Project type and purpose
• CineSync is a full-stack cinema management system. Based on the file tree and README, we see:
• A client folder (likely frontend code)
• A server folder containing a Node.js/Express REST API
• MongoDB as the primary datastore via Mongoose
The server handles user authentication (JWT), movie listings, watchlists, reviews, etc.
File structure
• Top-level:
• .env, config files, top-level README
• TechStorm (could be a placeholder)
• client – your frontend app (see its own README)
• server – your backend
• Under server:
• index.js / app.js – Express app setup, middleware registration
• controllers/ – business logic per resource (auth, movies, watchlist, listing)
• routes/ – HTTP routes mapped to controllers
• models/ – Mongoose schema definitions for Users, Movies, Playlists, Reviews, Watchlist
• db/ – database connection logic
• middleware/ – JWT auth guard, error handling
• utils/ – ApiError, ApiResponse, asyncHandler wrappers
README for additional insights
• Confirms tech stack: Node.js, Express, MongoDB/Mongoose, REST API, JWT, Dotenv
• Emphasis on backend; the client is separate but integrates via HTTP calls