How unmangeablealore/turnos-ganagana works
GanaGana is a four-counter queue system with customer-facing counter selection, a public spoken display, and administrator operations. The documented request path is React views → API client → Express routes/controllers → models → persistent store; Socket.IO separately coordinates live state and counter occupancy. The graph preserves authentication integrations, administration, scheduling, and live presence. Some UI and service modules are listed but unsampled, so their internal links are omitted unless documented or visible in the source index.
Main entry points: routes HTTP routes · pages Queue pages · caja.controller.js Counter operations · socket.controller.js Socket events
Components 27
React client
- Queue pages
client/src/views/pages - Admin console
client/src/views/admin - API client
client/src/controllers/api.ts - Client models
client/src/models - Spoken calls
client/src/controllers/voz.ts - Socket hook
client/src/controllers/useSocket.ts
HTTP application
- HTTP routes
server/routes - Authentication
server/controllers/auth.controller.js - Admin operations
server/controllers/administradores.controller.js - Queue operations
server/controllers/turno.controller.js - Counter operations
server/controllers/caja.controller.js - System settings
server/controllers/config.controller.js - Day management
server/controllers/sistema.controller.js - CAPTCHA check
server/services/captcha.service.js - OAuth providers
server/services/oauth.service.js
Live queue
- Socket events
server/controllers/socket.controller.js - Realtime service
server/services/tiempoReal.service.js - Device presence
server/models/presencia.model.js
Domain and persistence
- Queue state
server/models/turno.model.js - Settings model
server/models/configuracion.model.js - Administrator model
server/models/administrador.model.js - Jornada scheduler
server/services/jornada.service.js - Queue store
server/models/store.js
Other components
- Queue users
- Postgres
server/config/postgres.js - OAuth provider
- CAPTCHA provider
Connections 41
- Queue users → Queue pages: use
README.md - Queue pages → API client: request via
README.md - API client → HTTP routes: request
README.md - HTTP routes → Authentication: routes to
server/routes/auth.routes.js - HTTP routes → Admin operations: routes to
server/routes/auth.routes.js - HTTP routes → Queue operations: routes to
server/routes/api.routes.js - HTTP routes → Counter operations: routes to
server/routes/api.routes.js - HTTP routes → System settings: routes to
server/routes/api.routes.js - HTTP routes → Day management: routes to
server/routes/api.routes.js - Authentication → CAPTCHA check: verifies
server/controllers/auth.controller.js - Authentication → OAuth providers: delegates to
server/controllers/auth.controller.js - Authentication → Administrator model: looks up
server/controllers/auth.controller.js - Admin operations → Administrator model: uses
server/controllers/administradores.controller.js - Queue operations → Queue state: uses
server/controllers/turno.controller.js - Counter operations → Queue state: uses
server/controllers/caja.controller.js - Counter operations → Settings model: uses
server/controllers/caja.controller.js - Counter operations → Device presence: uses
server/controllers/caja.controller.js - Counter operations → Realtime service: emits updates
server/controllers/caja.controller.js - System settings → Settings model: uses
server/controllers/config.controller.js - System settings → Realtime service: emits updates
server/controllers/config.controller.js - Day management → Jornada scheduler: delegates to
server/controllers/sistema.controller.js - Jornada scheduler → Queue state: uses
server/services/jornada.service.js - Jornada scheduler → Settings model: uses
server/services/jornada.service.js - Jornada scheduler → Realtime service: emits updates
server/services/jornada.service.js - Queue state → Queue store: persists via
server/models/turno.model.js - Settings model → Queue store: reads and writes
server/models/configuracion.model.js - Administrator model → Queue store: uses
server/models/administrador.model.js - Queue store → Postgres: syncs data
server/models/store.js - Queue pages → Socket hook: uses live state
client/src/views/pages/CajaPage.tsx - Socket hook → Socket events: Socket.IO events
server/controllers/socket.controller.js - Socket events → Queue state: reads state
server/controllers/socket.controller.js - Socket events → Settings model: reads config
server/controllers/socket.controller.js - Socket events → Device presence: tracks devices
server/controllers/socket.controller.js - Socket events → Realtime service: delegates occupancy
server/controllers/socket.controller.js - Realtime service → Device presence: calculates presence
server/services/tiempoReal.service.js - Queue pages → Client models: uses
client/src/views/pages/CajaPage.tsx - Queue pages → Spoken calls: uses spoken calls
client/src/views/pages/DisplayPage.tsx - Admin console → API client: calls API
- Queue users → Authentication: admin sign-in
- OAuth providers → OAuth provider: redirects to
- CAPTCHA check → CAPTCHA provider: verifies with