How aldousroga/deskflow works
DeskFlow is an IT help-desk and asset-tracking application. Its principal workflow is signing in, then managing users and assets and submitting, triaging, and tracking tickets, including SLA clocks and history. The README also documents dashboard, technician, reporting, and settings capabilities. The backend is concentrated in Program.cs; excerpts are partial, so uncertain endpoint-to-feature wiring is omitted.
Main entry points: Program.cs HTTP API · app.html App shell · login.html Sign-in page · users.sql Users store
Components 21
Web interface
- Sign-in page
DeskFlow.Api/wwwroot/login.html - App shell
DeskFlow.Api/wwwroot/app.html
Identity and users
- Cookie authentication
DeskFlow.Api/Program.cs - User management
DeskFlow.Api/Program.cs - Users store
users.sql
Service operations
- Asset management
DeskFlow.Api/Program.cs - Assets store
assets.sql - Ticket lifecycle
DeskFlow.Api/Program.cs - Tickets store
tickets.sql - SLA tracking
DeskFlow.Api/Program.cs - SLA policies
sla_policies.sql - Ticket history
DeskFlow.Api/Program.cs
Insights and settings
- Dashboard
DeskFlow.Api/wwwroot/app.html - Technicians
DeskFlow.Api/wwwroot/app.html - Reports
DeskFlow.Api/wwwroot/app.html - Settings
DeskFlow.Api/Program.cs - Settings data
settings_tables.sql
Other components
- Staff or requester
- HTTP API
DeskFlow.Api/Program.cs - MySQL
- Google sign-in
Connections 24
- Staff or requester → Sign-in page: opens
- Sign-in page → HTTP API: signs in
- HTTP API → Cookie authentication: authenticates
- Cookie authentication → Users store: checks credentials
- Cookie authentication → Sign-in page: redirects
- Staff or requester → App shell: uses
- App shell → HTTP API: requests
- HTTP API → User management: dispatches
- HTTP API → Asset management: dispatches
- HTTP API → Ticket lifecycle: dispatches
- HTTP API → Settings: dispatches
- User management → Users store: reads/writes
- Asset management → Assets store: reads/writes
- Ticket lifecycle → Tickets store: reads/writes
- Ticket lifecycle → SLA tracking: gets policies
- SLA tracking → SLA policies: reads policies
- Ticket lifecycle → Ticket history: logs changes
- Ticket history → Tickets store: writes history
- HTTP API → Dashboard: serves app
- App shell → Technicians: shows view
- App shell → Reports: shows view
- Settings → Settings data: reads/writes
- HTTP API → MySQL: connects
- HTTP API → Google sign-in: supports optional sign-in