How olliefms/ollie works
ollie is a self-hosted freight TMS: fleet staff manage loads, trips, equipment, and facilities through a Fleet SPA/API or MCP, while drivers execute assigned trips through a mobile portal. Uploaded documents form a separate AI-processing capability, and background workers handle geocoding, routing, and recovery. The graph includes core operational data, auth, events, and both web clients. Several subsystems are represented from README statements and the source index; unsampled internals are not treated as inspected.
Main entry points: worker.rs Background workers · trip_lifecycle.rs Trip lifecycle · fleet_portal Fleet REST API · trips.rs Trip endpoints
Components 31
API surfaces
- Fleet REST API
src/api/fleet_portal - Fleet MCP
src/api/fleet_portal/mcp.rs - Driver portal API
src/api/driver_portal - OAuth endpoints
src/api/oauth
Fleet operations
- Trip lifecycle
src/services/trip_lifecycle.rs - Trip endpoints
src/api/trips.rs - Facility resolution
src/api/facilities.rs - Operational data store
src/db/mod.rs - Trip records
src/db/trip_ops.rs - Domain models
src/models/trip.rs - Event journal
src/events/mod.rs
Documents and AI
- Document endpoints
src/api/blobs.rs - Content-addressed files
src/storage/mod.rs - Extracted-text cache
src/storage/extract_store.rs - Document AI
src/ai/extract.rs
Background services
- Background workers
src/pipeline/worker.rs - Facility geocoding
src/pipeline/geocoding.rs - HGV routing
src/routing/mod.rs - Data integrity doctors
src/services/doctors
Web clients
- Fleet SPA
static/fleet/app.js - Fleet page router
static/fleet/router.js - Fleet API client
static/fleet/utils/api.js - Driver PWA
static/driver/app.js - Trip detail view
static/driver/pages/trip-detail.js - Driver API client
static/driver/utils/api.js
Other components
- Fleet staff / agents
- Drivers
- Ollama
- LanceDB vectors
- Geocoding services
- OpenRouteService
Connections 28
- Fleet staff / agents → Fleet REST API: uses
README.md - Fleet staff / agents → Fleet MCP: uses
README.md - Drivers → Driver portal API: uses
README.md - Fleet REST API → Trip endpoints: routes requests
- Trip endpoints → Trip lifecycle: calls
src/api/trips.rs - Trip lifecycle → Trip records: reads and writes
src/services/trip_lifecycle.rs - Trip lifecycle → Facility resolution: resolves stops
src/services/trip_lifecycle.rs - Trip records → Operational data store: persists
src/db/mod.rs - Trip endpoints → Domain models: uses
src/api/trips.rs - Trip lifecycle → Event journal: emits events
src/services/trip_lifecycle.rs - Fleet REST API → OAuth endpoints: authenticates
src/api/oauth/authorize.rs - Fleet SPA → Fleet page router: dispatches pages
static/fleet/app.js - Fleet SPA → Fleet API client: uses
static/fleet/app.js - Fleet API client → Fleet REST API: calls
- Driver PWA → Trip detail view: renders
static/driver/app.js - Trip detail view → Driver API client: uses
static/driver/pages/trip-detail.js - Driver API client → Driver portal API: calls
- Document endpoints → Content-addressed files: stores uploads
README.md - Content-addressed files → Background workers: queues processing
README.md - Background workers → Document AI: processes documents
README.md - Background workers → Extracted-text cache: caches extracted text
- Document AI → Ollama: requests summaries and embeddings
README.md - Document AI → LanceDB vectors: stores vectors
README.md - Background workers → Facility geocoding: runs geocoding
- Facility geocoding → Geocoding services: queries
- Background workers → HGV routing: runs routing
- HGV routing → OpenRouteService: requests HGV routes
src/routing/mod.rs - Background workers → Data integrity doctors: runs repairs