How jasphergayo/troddac works
TRODDAC is a role-based tricycle booking and operations portal. Its principal workflow runs from passenger booking and route/fare estimation through operator assignment, driver status/location updates, and passenger trip tracking or cancellation. Officer account administration is a separate capability. The source excerpts show shared authentication, booking/dispatch API behavior, and helper responsibilities; dashboards and several endpoints are unsampled, so their internal call links are omitted. The tree includes a mirrored troddac/ copy; this map represents the root application.
Main entry points: db.php Application data · auth.php Session and roles · driver_dashboard.php Driver dashboard · api.php API helpers
Components 26
Booking and trips
- Request a ride
passenger_book.php - Create booking
api/booking_create.php - Route and fare
api/route.php - Track or cancel
passenger_trip.php - Booking status
api/booking_status.php - Cancel booking
api/booking_cancel.php - Ride history
passenger_history.php
Dispatch operations
- Manual dispatch
operator_dispatch.php - Dispatch queue
api/operator_queue.php - Assign booking
api/operator_action.php - Driver dashboard
driver_dashboard.php - Trip actions
api/driver_action.php - Driver availability
api/driver_availability.php - Driver location
api/driver_location.php - Driver state
api/driver_state.php
Accounts and access
- Manage accounts
officer_users.php - Login
login.php - Passenger registration
register.php
Shared services
- Session and roles
config/auth.php - API helpers
config/api.php - Application data
config/db.php
Other components
- Passenger
- Operator
- Driver
- Association officer
- Map and routing services
Connections 33
- Passenger → Request a ride: requests ride
- Request a ride → Route and fare: requests route
- Request a ride → Create booking: submits booking
- Create booking → Application data: writes booking
api/booking_create.php - Create booking → API helpers: uses helpers
api/booking_create.php - Route and fare → API helpers: uses helpers
api/route.php - Route and fare → Map and routing services: requests routing
- Operator → Manual dispatch: assigns driver
- Manual dispatch → Dispatch queue: polls queue
- Manual dispatch → Assign booking: submits assignment
- Dispatch queue → Application data: reads dispatch data
api/operator_queue.php - Dispatch queue → API helpers: uses helpers
api/operator_queue.php - Assign booking → Application data: updates assignment
- Driver → Driver dashboard: updates trip
- Driver dashboard → Trip actions: submits actions
- Driver dashboard → Driver availability: changes availability
- Driver dashboard → Driver location: shares location
- Driver dashboard → Driver state: updates state
- Trip actions → Application data: updates trip
api/driver_action.php - Trip actions → API helpers: uses helpers
api/driver_action.php - Passenger → Track or cancel: tracks trip
- Track or cancel → Booking status: polls status
- Track or cancel → Cancel booking: requests cancel
- Booking status → Application data: reads booking
api/booking_status.php - Booking status → API helpers: uses helpers
api/booking_status.php - Association officer → Manage accounts: manages users
officer_users.php - Manage accounts → Application data: writes accounts
officer_users.php - Login → Session and roles: authenticates
login.php - Passenger registration → Session and roles: uses account rules
register.php - Session and roles → Application data: loads user
config/auth.php - Create booking → Session and roles: checks access
api/booking_create.php - Dispatch queue → Session and roles: checks access
api/operator_queue.php - Trip actions → Session and roles: checks access
api/driver_action.php