How tknushi/capstone-katokkalinis works
Katokkalinis is a municipal waste-management platform with resident, vendor, driver, inspector, and administrative workflows. Users enter through role-specific mobile screens; authentication services communicate with the Laravel API, whose routes dispatch requests to domain controllers. The backend covers vendor management, inspections, collection scheduling, attendance, incident reporting, and administration. The tree also contains separate resident/vendor and driver/inspector frontends. No README or frontend workflow excerpts were provided, so screen-to-service links and several domain details remain unverified.
Main entry points: Models Domain records · api.php API route dispatch · app Mobile role screens · auth.ts Mobile authentication
Components 17
Client apps
- Mobile role screens
Katokkalinis_mobile/app - Mobile authentication
Katokkalinis_mobile/services/auth.ts - Mobile API client
Katokkalinis_mobile/services/api.ts - Resident/vendor app
frontend/resident-vendor/app - Driver/inspector app
frontend/driver-inspector/app
API backend
- API route dispatch
backend/routes/api.php - Authentication
backend/app/Http/Controllers/Api/AuthController.php
Field operations
- Vendor management
backend/app/Http/Controllers/Api/VendorController.php - Market inspections
backend/app/Http/Controllers/Api/InspectionController.php - Collection schedules
backend/app/Http/Controllers/Api/ScheduleController.php - Staff attendance
backend/app/Http/Controllers/Api/AttendanceController.php - Pile-up incidents
backend/app/Http/Controllers/Api/ClenroPileupReportController.php - Operational analytics
backend/app/Http/Controllers/Api/AnalyticsController.php
Domain data
- Domain records
backend/app/Models - Application database
Other components
- Residents and staff
- API service
Connections 17
- Residents and staff → Mobile role screens: use role screens
- Mobile role screens → Mobile authentication: authenticate
- Mobile authentication → Mobile API client: calls
Katokkalinis_mobile/services/auth.ts - Mobile API client → API service: sends requests
- Resident/vendor app → API service: uses API
- Driver/inspector app → API service: uses API
- API service → API route dispatch: routes requests
- API route dispatch → Authentication: dispatches auth
backend/routes/api.php - API route dispatch → Vendor management: dispatches vendor routes
backend/routes/api.php - API route dispatch → Market inspections: dispatches inspection routes
backend/routes/api.php - API route dispatch → Staff attendance: dispatches attendance routes
backend/routes/api.php - Authentication → Domain records: reads and updates
backend/app/Http/Controllers/Api/AuthController.php - Vendor management → Domain records: reads and updates
backend/app/Http/Controllers/Api/VendorController.php - Staff attendance → Domain records: reads and updates
backend/app/Http/Controllers/Api/AttendanceController.php - Pile-up incidents → Domain records: queries incidents
backend/app/Http/Controllers/Api/ClenroPileupReportController.php - Operational analytics → Domain records: aggregates records
backend/app/Http/Controllers/Api/AnalyticsController.php - Domain records → Application database: persist records