How bashartomeza/masari works
Masari is an Arabic-first corridor logistics product with an admin console and API; the README also identifies an Android client, though its source is not present in this tree. A typical operational flow is route setup and publication, passenger or merchant demand entry, matching and capacity handling, then trip operations and admin monitoring. The graph emphasizes the documented route-management and canonical-dispatch path; sampled excerpts do not establish every client-to-API or service-to-database call, so uncertain links are omitted.
Main entry points: app.ts HTTP Application · App.tsx Admin App · previewService.ts Preview Service · canonicalDispatchWorker.ts Dispatch Worker
Components 23
Admin Console
- Admin App
apps/admin/src/App.tsx - Route Workspace
apps/admin/src/features/routes/RouteManagement.tsx - Dispatch Monitoring
apps/admin/src/features/monitoring/MatchingBatchingMonitoring.tsx - Overview Dashboard
apps/admin/src/features/overview/OverviewDashboard.tsx
API Surface
- HTTP Application
apps/api/src/app.ts
Route Management
- Route Endpoints
apps/api/src/modules/routeManagement.ts - Route Preview
apps/api/src/modules/routePreview.ts - Preview Service
apps/api/src/maps/previewService.ts - Map Providers
apps/api/src/maps/liveProviders.ts - Route Snapshot
apps/api/src/services/canonicalRouteSnapshots.ts
Demand Dispatch
- Passenger Demand
apps/api/src/modules/canonicalDemand.ts - Merchant Demand
apps/api/src/modules/merchant.ts - Canonical Matching
apps/api/src/modules/canonicalMatching.ts - Shared Matching
apps/api/src/modules/canonicalSharedMatching.ts - Dispatch Worker
apps/api/src/lib/canonicalDispatchWorker.ts
Operations
- Trip Operations
apps/api/src/modules/trips.ts - Driver Operations
apps/api/src/modules/driver.ts - Match Monitoring
apps/api/src/modules/adminMatchingMonitoring.ts - Monitoring Service
apps/api/src/services/adminMatchingMonitoring/service.ts - MySQL Database
Other components
- Admin
- Mobile User
- Map Services
Connections 34
- Admin → Admin App: uses
- Admin App → Route Workspace: renders
- Admin App → Overview Dashboard: renders
- Admin App → Dispatch Monitoring: renders
- Admin App → HTTP Application: requests
- Mobile User → HTTP Application: submits demand
- HTTP Application → Route Endpoints: dispatches
- HTTP Application → Route Preview: dispatches
- HTTP Application → Passenger Demand: dispatches
- HTTP Application → Merchant Demand: dispatches
- HTTP Application → Canonical Matching: dispatches
- HTTP Application → Shared Matching: dispatches
- HTTP Application → Trip Operations: dispatches
- HTTP Application → Driver Operations: dispatches
- HTTP Application → Match Monitoring: dispatches
- Route Endpoints → MySQL Database: reads/writes
- Route Preview → Preview Service: calls
- Preview Service → MySQL Database: reads
- Preview Service → Map Providers: requests routes
- Map Providers → Map Services: queries
- Passenger Demand → Route Snapshot: snapshots route
- Merchant Demand → Route Snapshot: snapshots route
- Canonical Matching → MySQL Database: reads/writes
- Shared Matching → MySQL Database: reads/writes
- Dispatch Worker → Canonical Matching: runs/expunges
- Dispatch Worker → Shared Matching: runs/expunges
- HTTP Application → Dispatch Worker: starts
- Trip Operations → MySQL Database: reads/writes
- Driver Operations → MySQL Database: reads/writes
- Match Monitoring → Monitoring Service: calls
- Monitoring Service → MySQL Database: reads
- Dispatch Monitoring → HTTP Application: requests monitoring
- Overview Dashboard → HTTP Application: loads overview
- Route Workspace → HTTP Application: manages routes