How divyanshu2003singh/trip-tide works
Project type and purpose
• Triptide is a full-stack MERN (MongoDB, Express, React, Node) ride-sharing application.
• Purpose: allow customers to create ride requests, drivers to accept and manage rides, with real-time updates, geospatial filtering (5 km radius via Mapbox), and post-ride rating.
File structure
• Top-level directories:
• Backend/
– Controller: commonController.js, rideController.js, userController.js
– Router: commonRouter.js, rideRouter.js, userRouter.js
– Model: config.js, rideModel.js, userModel.js
– Middleware: userAuth.js
– util: rideUtil.js
• Frontend/
– public/: index.html, _redirects
– src/: index.js, pages/… (React component per page)
• Pattern:
• Backend follows MVC (Models, Controllers, Routers) plus a middleware layer and utilities.
• Frontend uses component-based React pages and static assets under public.
README for additional insights
• Key technologies: MongoDB, Express.js, React.js, Node.js, Socket.io, Mapbox API, JWT.
• Features: user auth, create/accept rides, real-time updates via Socket.io, rating system, ride status updates.
• External dependencies: Mapbox for geolocation/distance, JWT for auth tokens, real-time channel via WebSocket.
Detail without over-fragmenting
• Major page in the Frontend cluster if desired (Login, Signup, Map view, Ride list).
• Don’t omit the .env config (PORT, MONGODB_URI, JWT_SECRET) – indicate configuration as a note or side artifact.