zaantoru/p2p-ui

Purpose and entry points

1816 is a peer-to-peer car and motorcycle rental platform. A React/Vite client serves renter and role-specific staff workflows; a Fastify API owns booking, payment, operations, notifications, and telemetry persistence. Client startup is src/main.jsx → src/App.jsx; API startup is server/src/index.js. Vite proxies browser /api and /uploads traffic to the API.

Client application and role workspaces

The SPA provides vehicle discovery, detail, checkout, chat, notifications, and dashboards for renter, host, operations, management, and admin roles. Authentication state is centralized before protected API interactions, while dashboard selection reflects server-issued roles.

• src/context/AuthContext.jsx

• src/pages/Checkout/Checkout.jsx

• src/pages/Dashboard/Renter/RenterDashboard.jsx

• src/pages/Dashboard/Operations/OperationsDashboard.jsx

• src/pages/Dashboard/Admin/AdminDashboard.jsx

API boundary, identity, and authorization

Fastify routes expose the domain API. JWT authentication and role guards form the principal boundary between the SPA and protected booking, operational, financial, and fleet actions. Uploads are served separately for vehicle and workflow evidence.

• server/src/index.js

• server/src/routes/auth.js

• server/src/middleware/auth.js

• server/src/middleware/roleGuard.js

• server/src/routes/uploads.js

Booking lifecycle and availability control

Bookings progress through approval, payment-required, scheduled/booked, ongoing, and completed states. Route handlers coordinate availability, workflow state, and notifications; overlap/hold logic prevents conflicting reservations. Late status and fee calculation are modeled separately from booking status.

• server/src/routes/bookings.js

• server/src/routes/operations.js

• server/src/utils/bookingOverlap.js

• server/src/utils/lateFees.js

• server/src/services/lateReturnMonitor.js

Payments, receipts, and payment policy

The platform supports manually verified GCash/Maya evidence, with a fixed PHP 1 test-reservation policy after approval. It also contains PayMongo checkout/webhook integration, receipt generation, payment-method management, and refund eligibility/policy rules.

• server/src/routes/payments.js

• server/src/routes/paymentMethods.js

• server/src/routes/paymongoWebhooks.js

• server/src/services/paymongoService.js

• server/src/services/receiptService.js

Evidence-led rental operations

Operational routes manage pre-handover and post-return condition checks, required renter sign-off, and completion. Identity and requirements endpoints support renter verification and required booking documentation; stored uploads are an important persistence boundary.

• server/src/routes/conditionChecks.js

• server/src/routes/identity.js

• server/src/routes/requirements.js

• server/uploads/vehicle-photos

Fleet, telemetry, and communications

Vehicle inventory is managed through the vehicle API and host workflows. MQTT/GNSS telemetry is ingested for registered IoT devices, with a staff-only simulation path outside production. The API also supports direct messages, in-app notifications, booking reminders, and email delivery.

• server/src/routes/vehicles.js

• server/src/routes/telemetry.js

• server/src/services/telemetryService.js

• server/src/routes/messages.js

• server/src/services/mailService.js

Persistence and infrastructure

PostgreSQL is the system of record, accessed through the DB configuration and evolved by ordered SQL migrations tracked in schema_migrations. Runtime dependencies include Node.js/Fastify, PostgreSQL, JWT, MQTT broker connectivity, PayMongo, and local upload storage.

• server/src/config/db.js

• server/db/schema.sql

• server/db/migrations/001_operations_upgrade.sql

• server/db/migrations/004_paymongo_checkout_webhooks.sql

• server/scripts/migrate.js