How en-gu/e-ticket-bapenda works
This is a Next.js online queue-ticketing system for Bapenda Kabupaten Garut: visitors register and track tickets, while officers validate arrivals and manage the queue, and admins manage services, sessions, tickets, and reports. The graph preserves those distinct stages and the shared Supabase-backed data layer. Some UI-to-API links are documented at the product level but not shown in sampled source, so those links are dashed; unsampled subsystems are represented by their existing directories.
Main entry points: dashboard/page.tsx Admin dashboard · supabase-server.ts Server database client · dashboard/page.tsx Queue dashboard · daftar/page.tsx Ticket registration
Components 24
Visitor portal
- Ticket registration
frontend/src/app/daftar/page.tsx - Services and sessions
frontend/src/app/api - Create ticket
frontend/src/app/api/tickets/route.ts - Track ticket
frontend/src/app/cek/page.tsx - Ticket lookup API
frontend/src/app/api/tickets/[code]/route.ts - E-ticket page
frontend/src/app/tiket/[bookingCode]/page.tsx - Print and download
frontend/src/app/tiket/[bookingCode]/ETicketClient.tsx - Ticket presentation
frontend/src/components/tiket/ETicket.tsx
Officer operations
- Officer login
frontend/src/app/petugas/login/page.tsx - Login API
frontend/src/app/api/auth/login/route.ts - Queue dashboard
frontend/src/app/petugas/dashboard/page.tsx - Ticket validation
frontend/src/app/api/petugas/scan/route.ts - Queue actions
frontend/src/app/api/petugas - Queue status
frontend/src/app/api/queue/status/route.ts
Admin management
- Admin dashboard
frontend/src/app/admin/dashboard/page.tsx - Ticket management
frontend/src/app/api/admin/tickets/route.ts - Service management
frontend/src/app/api/admin/services - Session management
frontend/src/app/api/admin/sessions - Reports
frontend/src/app/api/admin/laporan/route.ts
Shared data layer
- Server database client
frontend/src/lib/supabase-server.ts - Supabase database
Other components
- Visitor
- Officer
- Admin
Connections 23
- Visitor → Ticket registration: registers
README.md - Ticket registration → Services and sessions: chooses options
- Ticket registration → Create ticket: submits details
- Create ticket → Server database client: uses client
frontend/src/app/api/tickets/route.ts - Server database client → Supabase database: reads and writes
- Visitor → Track ticket: tracks ticket
README.md - Track ticket → Ticket lookup API: looks up ticket
- E-ticket page → Print and download: renders
frontend/src/app/tiket/[bookingCode]/page.tsx - Print and download → Ticket presentation: renders
frontend/src/app/tiket/[bookingCode]/ETicketClient.tsx - E-ticket page → Server database client: loads ticket
frontend/src/app/tiket/[bookingCode]/page.tsx - Officer → Officer login: signs in
README.md - Officer login → Login API: authenticates
- Officer → Queue dashboard: manages queue
README.md - Queue dashboard → Ticket validation: validates code
- Ticket validation → Server database client: reads and updates
frontend/src/app/api/petugas/scan/route.ts - Queue dashboard → Queue actions: controls queue
- Queue dashboard → Queue status: views status
- Admin → Admin dashboard: manages system
README.md - Admin dashboard → Ticket management: manages tickets
- Admin dashboard → Service management: manages services
- Admin dashboard → Session management: manages sessions
- Admin dashboard → Reports: views reports
- Reports → Server database client: queries tickets
frontend/src/app/api/admin/laporan/route.ts