glyphcoder/odoo_coryd

Purpose and Entry Points

Enterprise CoRYD is a multi-tenant employee carpooling platform: users offer/find rides, book and manage trips, share live location, chat/call, and settle fares; organization admins oversee users, vehicles, and reports. The React SPA starts at client/src/main.jsx and client/src/App.jsx. The Node API and Socket.IO server start at server/src/index.js.

Client Application

The Vite React client owns authenticated navigation, role-oriented dashboards, and trip workflows. Authentication state is centralized in client/src/auth/AuthContext.jsx; REST calls and realtime client setup are separated into client/src/api.js and client/src/socket.js. Core user journeys are implemented by client/src/pages/FindRide.jsx, client/src/pages/OfferRide.jsx, and client/src/pages/TripDetail.jsx; administrative oversight is in client/src/pages/AdminDashboard.jsx.

API and Authorization Boundary

Express exposes JWT-protected /api route groups, with login/signup as the public boundary. JWT middleware in server/src/middleware/auth.js establishes identity and organization context before route handlers. Domain APIs are divided across server/src/routes/rides.js, server/src/routes/bookings.js, server/src/routes/trips.js, and related payment, wallet, vehicle, reporting, and admin route modules. Server configuration and PostgreSQL access are centralized in server/src/config.js and server/src/db.js.

Tenant Data Model and Isolation

PostgreSQL/Supabase is the system of record. The schema at db/schema.sql models organization-scoped tenant data, while db/migrations/add_vehicle_documents.sql evolves vehicle support. Tenant isolation is designed through organization-filtered queries, composite organization-aware foreign keys, and optional Postgres RLS policies in db/rls.sql. Database provisioning and demo data execution flow through server/migrate.js and server/scripts/seed.js.

Ride, Booking, and Trip Lifecycle

A driver publishes a ride; riders search and create bookings; the resulting trip progresses through status transitions and produces trip history, messages, and location pings. Server-side lifecycle ownership is concentrated in server/src/routes/rides.js, server/src/routes/bookings.js, and server/src/routes/trips.js. The UI consumes this flow primarily through client/src/pages/FindRide.jsx and client/src/pages/TripDetail.jsx.

Realtime Trips and Communications

Socket.IO provides a per-trip realtime boundary: participants join only authorized trip rooms, then exchange location updates, chat, presence, and WebRTC signaling. The server implementation is server/src/sockets/index.js; the client socket transport is client/src/socket.js. Live map rendering and peer audio behavior reside in client/src/components/MapView.jsx, client/src/components/AudioCallOverlay.jsx, and client/src/hooks/useWebRTC.js. Browser Geolocation feeds live tracking; WebRTC carries peer-to-peer audio after Socket.IO signaling.

External Services and Integrations

The runtime requires Node 18+ and PostgreSQL 14+ or Supabase. Geocoding, reverse lookup, and route calculation are proxied through server/src/routes/geo.js, using public Nominatim, OpenStreetMap, and OSRM services. Payment/wallet handling is split between server/src/routes/payments.js and server/src/routes/wallet.js, with Razorpay-oriented client controls in client/src/components/RazorpayButton.jsx and client/src/components/RazorpayQR.jsx; non-wallet card/UPI behavior is currently sandbox-oriented.