How hariharan-2754/garments-workflow works
GarmentFlow is a garment-workflow task management app for administrators and department workers. Administrators manage workers, departments, and tasks; workers view department tasks and submit completion outcomes. The browser clients use a shared API helper to communicate with a FastAPI backend, which applies authentication and persists users, departments, and tasks using MongoDB when configured or a local JSON-backed mock database otherwise. The README excerpt is unreadable, so capability coverage is based on the available tree and source index; unsampled UI behavior and route wiring are not inferred.
Main entry points: db.py Database adapter · app.py FastAPI app · auth.py Authentication · api.js API client
Components 21
Browser interface
- Admin screens
frontend/js/dashboard.js - Task assignment
frontend/js/assign-task.js - Department screens
frontend/js/departments.js - Worker screens
frontend/js/workers.js - Worker task list
frontend/js/worker-home.js - Worker task detail
frontend/js/worker-task.js
HTTP and access
- API client
frontend/js/api.js - FastAPI app
backend/app.py - Authentication
backend/middleware/auth.py
Workflow domains
- Login API
backend/routes/auth.py - Department API
backend/routes/departments.py - Worker API
backend/routes/workers.py - Task API
backend/routes/tasks.py - User data model
backend/models/user.py - Department model
backend/models/department.py - Task data model
backend/models/task.py
Configuration and data
- Runtime settings
backend/config/settings.py - Database adapter
backend/config/db.py - Local JSON data
backend/db.json
Other components
- MongoDB
- Admin or worker
Connections 31
- Admin or worker → Admin screens: uses
- Admin or worker → Worker task list: uses
- Admin screens → API client: calls
frontend/js/dashboard.js - Task assignment → API client: calls
frontend/js/assign-task.js - Department screens → API client: calls
frontend/js/departments.js - Worker screens → API client: calls
frontend/js/workers.js - Worker task list → API client: calls
frontend/js/worker-home.js - Worker task detail → API client: calls
frontend/js/worker-task.js - Worker task detail → Task API: updates status
frontend/js/worker-task.js - FastAPI app → Runtime settings: loads
backend/app.py - FastAPI app → Database adapter: connects
backend/app.py - FastAPI app → Login API: registers
backend/app.py - FastAPI app → Department API: registers
backend/app.py - FastAPI app → Worker API: registers
backend/app.py - FastAPI app → Task API: registers
backend/app.py - Login API → Database adapter: reads users
backend/routes/auth.py - Login API → Authentication: creates tokens
backend/routes/auth.py - Login API → User data model: validates input
backend/routes/auth.py - Department API → Database adapter: reads and writes
backend/routes/departments.py - Department API → Authentication: checks access
backend/routes/departments.py - Department API → Department model: validates input
backend/routes/departments.py - Worker API → Database adapter: reads and writes
backend/routes/workers.py - Worker API → Authentication: checks access
backend/routes/workers.py - Worker API → User data model: validates input
backend/routes/workers.py - Task API → Database adapter: reads and writes
backend/routes/tasks.py - Task API → Authentication: checks access
backend/routes/tasks.py - Task API → Task data model: validates status
backend/routes/tasks.py - Authentication → Database adapter: loads user
backend/middleware/auth.py - Authentication → Runtime settings: uses JWT settings
backend/middleware/auth.py - Database adapter → Local JSON data: reads and writes
backend/config/db.py - Database adapter → MongoDB: connects optionally
backend/config/db.py