How fenderrex/chair works
This is a Flask/MySQL rideshare demonstration with separate passenger, driver, and admin experiences. Its central workflow is route/fare estimation, ride request, nearby-driver offers, acceptance, trip lifecycle updates, and live client updates. The graph also preserves documented messaging, location ingestion and simulation, admin operations, signup, payments, identity, and surveys. Some subsystem links rely on README statements because their source was not excerpted; edges are omitted where the caller relationship was not evidenced.
Main entry points: routes.py Trip routes · driver.js Driver screen · proximity.py Driver dispatch · pipeline.py Location ingestion
Components 28
User experiences
- Passenger screen
app/static/js/passenger.js - Driver screen
app/static/js/driver.js - Admin screen
app/static/js/admin.js - Signup and auth
app/auth/services.py
Ride workflow
- Trip routes
app/trips/routes.py - Route and fare
app/maps/services.py - Request handling
app/trips/requests_service.py - Driver dispatch
app/dispatch/proximity.py - Trip lifecycle
app/trips/lifecycle.py - Trip state
app/trips/state.py - Live trip updates
app/trips/stream.py - Trip messaging
app/messages/services.py
Operations and location
- Driver services
app/drivers/services.py - Location ingestion
app/location/pipeline.py - GPS provider
app/location/providers/gps.py - Demo simulation
app/broker/demo_service.py - Admin operations
app/admin/services.py - Identity processing
app/id_processing/services.py - Payments
app/payments/services.py - Trip surveys
app/surveys/routes.py
Data and integrations
- MySQL data
app/extensions.py - Trip records
app/trips/models.py - Driver records
app/drivers/models.py - User records
app/users/models.py - Socket.IO
app/extensions.py
Other components
- Passenger
- Driver
- Admin
Connections 32
- Passenger → Passenger screen: uses
- Driver → Driver screen: uses
- Admin → Admin screen: uses
- Passenger screen → Trip routes: requests rides
- Trip routes → Route and fare: estimates route
app/trips/routes.py - Trip routes → Request handling: creates requests
- Request handling → Driver dispatch: offers rides
app/trips/requests_service.py - Driver → Driver dispatch: accepts offer
- Driver screen → Trip routes: acts on trips
app/trips/routes.py - Trip routes → Trip lifecycle: updates lifecycle
- Trip lifecycle → Trip state: changes state
- Trip routes → Live trip updates: publishes snapshots
app/trips/routes.py - Live trip updates → Socket.IO: broadcasts updates
app/trips/stream.py - Passenger screen → Trip messaging: messages driver
- Driver screen → Trip messaging: messages passenger
- Trip messaging → MySQL data: stores messages
- GPS provider → Location ingestion: submits coordinates
app/location/providers/gps.py - Location ingestion → Driver records: updates location
- Driver services → Driver records: manages drivers
app/drivers/services.py - Driver screen → Location ingestion: sends GPS
- Admin screen → Admin operations: manages platform
- Admin operations → Trip records: reads trip activity
app/admin/services.py - Admin → Demo simulation: controls simulation
- Demo simulation → Location ingestion: feeds simulated locations
- Passenger → Signup and auth: signs up
- Signup and auth → User records: persists account
- Identity processing → MySQL data: stores identity data
- Payments → MySQL data: stores payment data
- Trip surveys → MySQL data: stores survey data
app/surveys/routes.py - Request handling → Trip records: persists requests
app/trips/requests_service.py - Driver dispatch → Driver records: checks candidates
app/dispatch/proximity.py - Driver dispatch → Trip records: creates offers
app/dispatch/proximity.py