amit2003dh/co-ride-app

Purpose and deployment

Co-Ride is a MERN ride-sharing marketplace: authenticated users offer rides, discover/book rides, manage active/history views, submit reviews/feedback, and use rider/passenger/admin capabilities. The React/Vite client is deployed to Vercel; the Express API is intended for Render and persists data in MongoDB Atlas.

Application entry points

• Client bootstrap and route composition: client/src/main.jsx, client/src/App.jsx.

• API process and Socket.IO server bootstrap: server/server.js.

• Database connection boundary: server/config/db.js.

• Environment-specific client/server settings are represented by client/.env.example and server/.env.example.

Frontend navigation and access control

React Router pages form the user workflow: public home/login/registration, ride search/offer/dashboard/profile, active rides, ride history, and administration. Route guards separate authenticated and admin-only flows via client/src/components/PrivateRoute.jsx and client/src/components/AdminRoute.jsx.

Key product screens are client/src/pages/FindRidePage.jsx, client/src/pages/OfferRidePage.jsx, and client/src/pages/ActiveRidePage.jsx; dashboard variants are client/src/pages/DashboardPage.jsx and client/src/pages/AdminDashboardPage.jsx.

Client state and API boundary

Redux Toolkit centralizes domain state. Each domain pairs a slice with a service that calls the backend: authentication (client/src/store/auth/authSlice.js, client/src/store/auth/authService.js), rides (client/src/store/ride/rideSlice.js, client/src/store/ride/rideService.js), and payments (client/src/store/payment/paymentSlice.js, client/src/store/payment/paymentService.js). The root store is client/src/store/store.js.

UI components consume this state and drive interactive ride operations, including map/chat-oriented views in client/src/components/LiveMap.jsx and client/src/components/ChatBox.jsx. Socket.IO-client supports real-time interactions.

HTTP API and authorization pipeline

Express routes partition the API by domain: server/routes/auth.js, server/routes/rides.js, server/routes/payment.js, server/routes/admin.js, plus user, review, and feedback routes. Routes delegate request handling to corresponding controllers, notably server/controllers/authController.js, server/controllers/rideController.js, and server/controllers/paymentController.js.

JWT authentication is enforced at the middleware boundary in server/middleware/authMiddleware.js; privileged operations add server/middleware/adminMiddleware.js. This makes controllers responsible for domain operations after identity/role validation.

Core persistence model

MongoDB/Mongoose is the system of record. server/models/User.js owns accounts, credentials, and roles; server/models/Ride.js represents offered/booked ride lifecycle data. Reputation and support data are modeled separately in server/models/Review.js and server/models/Feedback.js.

Primary flow: a user authenticates, the client stores/uses authenticated state, protected requests reach ride controllers, ride changes persist through Mongoose, and UI state is refreshed or updated through Redux and real-time Socket.IO events.

Supporting product boundaries

Payment handling is isolated behind server/routes/payment.js and server/controllers/paymentController.js, with client orchestration in client/src/store/payment/paymentService.js. Reviews and feedback similarly remain distinct domains through server/controllers/reviewController.js and server/controllers/feedbackController.js, surfaced by client/src/components/ReviewModal.jsx and client/src/components/FeedbackModal.jsx.