How borgolov/webqueue2 works
This appears to be a Flask-based service-ticket and queue application with browser clients for terminals, staff, and public displays. The main user journey is selecting a service at a terminal, managing the resulting ticket through staff workflows, and announcing calls on a display; the sampled terminal and display clients show API and Socket.IO interactions, but the server-side event wiring was not sampled. The graph also preserves authentication, administration, API testing, and chat capabilities visible in the tree. Links to unsampled server subsystems are omitted where their wiring cannot be established.
Main entry points: terminalapp.js Service Terminal · resources.py API Resources · views.py Frontend Routes · sqlite3.db SQLite Database
Components 18
Queue Clients
- Service Terminal
app/static/terminal_hybrid/js/terminalapp.js - Queue Display
app/static/screen_new/js/screenapp.js - Worker Interface
app/static/worker_new/js/mainapp.js
Application Server
- Frontend Routes
app/frontend/views.py - API Resources
app/api/resources.py - API Schemas
app/api/shemes.py - Socket Handlers
app/socket.py
Queue Domain
- Ticket Queue
app/queue.py - Domain Models
app/models.py - SQLite Database
instance/sqlite3.db
Supporting Features
- Authentication
app/auth/views.py - Queue Admin
app/admin_queue/routes.py - Socket API Tester
app/static/api_tester/js/app.c77a4a72.js - Simple Chat
app/static/vue_simple_chat/js/app.cb8765da.js
Other components
- Operator
- HTTP API
- Socket.IO Service
- Browser User
Connections 19
- Operator → Service Terminal: uses
- Service Terminal → HTTP API: requests settings
- HTTP API → API Resources: routes requests
- API Resources → API Schemas: serializes
- Service Terminal → Socket.IO Service: emits ticket events
- Socket.IO Service → Socket Handlers: dispatches events
- Queue Display → HTTP API: loads settings
- Queue Display → Socket.IO Service: subscribes to updates
- Worker Interface → Socket.IO Service: connects
- Frontend Routes → SQLite Database: queries locations
- Frontend Routes → Browser User: renders pages
- Authentication → SQLite Database: loads users
- API Resources → SQLite Database: queries records
- Ticket Queue → Domain Models: uses domain records
- Browser User → Socket API Tester: tests socket API
- Socket API Tester → Socket.IO Service: emits messages
- Browser User → Simple Chat: uses chat
- Simple Chat → Socket.IO Service: emits chat events
- Browser User → Frontend Routes: requests pages