How rahulks01/bequem works
Project type and purpose
• This is a full‑stack, real‑time cab‑booking application called βequem.
• Frontend: React + Vite for User and Captain (driver) interfaces.
• Backend: Node.js/Express API with Socket.IO for real‑time events, MongoDB for persistence, and Google Maps API for geocoding and maps.
File structure
• Top-level directories:
• Backend/ – Express app with MVC‑style structure:
– controllers/ (HTTP handlers)
– services/ (business logic)
– models/ (Mongoose schemas)
– routes/ (REST endpoints)
– middlewares/ (auth)
– db/ (DB connection)
– socket.js (real‑time events bootstrapping)
• Frontend/ – Vite‑powered React app:
– src/pages/ (route‑level components for User & Captain flows)
– src/components/ (UI pieces: ride popups, tracking, etc.)
– src/context/ (React Context for User, Captain, Socket)
– public/, index.html, config files
Key insights from README
• Real‑time ride requests: user searches locations → ride requested → backend notifies nearby captains via WebSocket → captain accepts → OTP handshake → ride lifecycle → trip completion resets UI.
• External dependencies: MongoDB, JWT for auth, Google Maps API, Socket.IO real‑time layer.