How fauzaro01/antriyuk works
AntriYuk is a web-based queue management system. Customers choose a service location, take or check a ticket, and can follow queue updates; operators assign counters and advance tickets through calling, serving, completion, or skipping. Admins manage locations, counters, users, and service categories, while reports summarize ticket and feedback activity. The README documents estimated waits and a live display board. Sampled source confirms operator actions and admin/report queries; unsampled controller and event wiring is represented only at the documented capability level.
Main entry points: AdminController.php Admin Controller · OperatorController.php Operator Controller · Ticket.php Ticket State · ReportController.php Report Controller
Components 24
Customer Intake
- Ticket Controller
app/Http/Controllers/TicketController.php - Booking Controller
app/Http/Controllers/BookingController.php - Location Controller
app/Http/Controllers/LocationController.php - Feedback Controller
app/Http/Controllers/FeedbackController.php
Queue Operations
- Operator Controller
app/Http/Controllers/OperatorController.php
Administration
- Admin Controller
app/Http/Controllers/AdminController.php - Report Controller
app/Http/Controllers/ReportController.php - Auth Controller
app/Http/Controllers/AuthController.php
Queue Domain
- Ticket State
app/Models/Ticket.php - Booking
app/Models/Booking.php - Location
app/Models/Location.php - Counter
app/Models/Counter.php - Service Category
app/Models/ServiceCategory.php - Feedback
app/Models/Feedback.php - User
app/Models/User.php
Live Experience
- Queue Events
app/Events/QueueUpdated.php - Ticket Events
app/Events/TicketCreated.php - Echo Client
resources/js/echo.js - Web Views
resources/views
Other components
- Customer
- Operator
- Administrator
- Application Database
- Reverb WebSocket
Connections 39
- Customer → Location Controller: browses locations
- Customer → Ticket Controller: takes or checks
- Customer → Booking Controller: makes booking
- Customer → Feedback Controller: submits feedback
- Operator → Operator Controller: manages queue
- Administrator → Admin Controller: manages system
- Administrator → Report Controller: views reports
- Customer → Auth Controller: authenticates
- Operator Controller → Ticket State: advances status
- Operator Controller → Counter: assigns counter
- Operator Controller → Location: reads queue
- Operator Controller → Queue Events: broadcasts updates
- Admin Controller → Location: manages locations
- Admin Controller → Counter: manages counters
- Admin Controller → User: manages users
- Admin Controller → Service Category: manages categories
- Admin Controller → Ticket State: counts tickets
- Report Controller → Ticket State: aggregates tickets
- Report Controller → Feedback: summarizes feedback
- Ticket Controller → Ticket State: creates or checks
- Booking Controller → Booking: creates or checks
- Location Controller → Location: reads locations
- Feedback Controller → Feedback: records feedback
- Ticket Controller → Ticket Events: emits ticket events
- Ticket State → Application Database: persists state
- Booking → Application Database: persists bookings
- Location → Application Database: persists locations
- Counter → Application Database: persists counters
- Service Category → Application Database: persists categories
- Feedback → Application Database: persists feedback
- User → Application Database: persists users
- Queue Events → Reverb WebSocket: broadcasts event
- Ticket Events → Reverb WebSocket: broadcasts event
- Echo Client → Reverb WebSocket: subscribes updates
- Reverb WebSocket → Echo Client: delivers updates
- Echo Client → Web Views: updates display
- Operator Controller → Web Views: renders dashboard
- Admin Controller → Web Views: renders admin pages
- Report Controller → Web Views: renders reports