How gokul-vs-kannan/lmts works
This is a Django-based fleet/transport management application, organized into role and domain apps. The visible workflow is a user request handled by a role-specific view, which uses domain models; driver, mechanic, and owner views have indexed references to related models. The tree also identifies home, user, and vehicle apps, but their behavior was not sampled. No README is present, so the product’s detailed capabilities and URL routing cannot be confirmed; dashed links mark the unverified request entry points.
Main entry points: owner/views.py Owner views · driver/views.py Driver views · mechanic/views.py Mechanic views · models.py Vehicle records
Components 11
Access and Home
- User records
lmts_project/user/models.py - Home views
lmts_project/home/views.py
Fleet Roles
- Driver views
lmts_project/driver/views.py - Driver records
lmts_project/driver/models.py - Mechanic views
lmts_project/mechanic/views.py - Mechanic records
lmts_project/mechanic/models.py - Owner views
lmts_project/owner/views.py - Owner records
lmts_project/owner/models.py
Fleet Records
- Vehicle views
lmts_project/vehicle/views.py - Vehicle records
lmts_project/vehicle/models.py
Other components
- Web user
Connections 13
- Web user → Home views: requests
- Web user → Driver views: requests
- Web user → Mechanic views: requests
- Web user → Owner views: requests
- Web user → Vehicle views: requests
- Driver views → Vehicle records: references
lmts_project/driver/views.py - Driver views → Owner records: references
lmts_project/driver/views.py - Mechanic views → Owner records: references
lmts_project/mechanic/views.py - Mechanic views → Vehicle records: references
lmts_project/mechanic/views.py - Owner views → Driver records: references
lmts_project/owner/views.py - Owner views → Mechanic records: references
lmts_project/owner/views.py - Owner views → User records: references
lmts_project/owner/views.py - Owner views → Vehicle records: references
lmts_project/owner/views.py