How roh0308/rohit_petpooja works
Project type and purpose
• From the file tree and README, this is the backend portion of a full-stack restaurant management application (“PetPooja”).
• Features: session-based table order tracking, real-time inventory management, sales dashboard, bill generation, menu CRUD.
• There is a separate frontend (started via npm run dev on port 3000) that calls this backend (port 3001).
File structure
• Top-level:
• app.js – entry point, sets up Express server and middleware
• config/db.js – database connection logic
• routes/ – Express route modules:
– billingRoutes.js
– dashboardRoutes.js
– menuRoutes.js
– tableRoutes.js
• package.json / lock – dependencies (likely Express, database driver, maybe socket.io)
• No controllers/services directory, but routes folder suggests an MVC‐style pattern (routes → controllers → DB).
README for additional insights
• We know the backend exposes REST endpoints consumed by a frontend.
• Database (SQL or NoSQL) holds tables for menu, orders, sessions, inventory.
Emphasize
• Every logical component (UI, API, DB, real-time layer).
• Data flow direction clearly.