How hesersu/menu-please-server works
Project type and purpose
• This is a Node.js/Express REST API back‑end (no separate front‑end code present).
• It manages Restaurants, Menus and Users, handles authentication via JWT, stores images via Cloudinary, and even integrates with an external “gemini” AI service.
File structure
• Top‑level entry points: server.js (starts the HTTP server) and app.js (configures Express).
• config/ holds environment settings.
• db/ establishes the database connection (e.g., MongoDB).
• models/ defines Mongoose (or ORM) schemas for Users, Restaurants, Menus.
• middlewares/ contains cross‑cutting concerns: jwt.middleware.js for authentication, cloudinary.middleware.js for image uploads.
• error-handling/ centralizes error formatter and handler.
• routes/ wires URL paths to controller logic: auth.routes, restaurants.routes, menus.routes, gemini.routes.
• vercel.json indicates deployment on Vercel (serverless or hosting config).
README for additional insights
• README only gives the project name, but combined with the file tree we know it’s a back‑end API service for menu management.