How sakh1l/quizhub works
QuizHub is a single-binary, real-time multiplayer trivia game. Hosts authenticate, manage reusable quizzes, open a room, and control game pacing; players join by code, answer timed questions, and see results and rankings. The server coordinates HTTP handlers, persistent SQLite state, and WebSocket updates, while embedded browser clients provide the host and player experiences. The README documents major product flows; unsampled admin and question-handler details are represented at their known source paths, with links limited to documented relationships.
Main entry points: handler.go Route registry · hub.go WebSocket hub · main.go HTTP server · room.go Room and joining
Components 17
Browser clients
- Admin panel
web/static/admin.js - Player app
web/static/app.js - Embedded assets
web/embed.go
Quiz and game
- Admin access
internal/handlers/auth.go - Quiz library
internal/handlers/quizzes.go - Question management
internal/handlers/questions.go - Room and joining
internal/handlers/room.go - Game and scoring
internal/handlers/game.go - Join QR code
internal/handlers/qr.go - Domain models
internal/models/models.go
Server runtime
- HTTP server
cmd/server/main.go - Route registry
internal/handlers/handler.go - HTTP middleware
internal/middleware/middleware.go - WebSocket hub
internal/ws/hub.go
Persistence
- SQLite state
internal/db/db.go
Other components
- Host
- Player
Connections 27
- Host → Admin panel: operates
README.md - Player → Player app: uses
README.md - Admin panel → Route registry: calls API
README.md - Player app → Route registry: calls API
web/static/app.js - Player app → WebSocket hub: receives updates
README.md - Admin panel → WebSocket hub: receives updates
README.md - HTTP server → Route registry: registers routes
cmd/server/main.go - HTTP server → SQLite state: opens store
cmd/server/main.go - HTTP server → WebSocket hub: starts hub
cmd/server/main.go - HTTP server → HTTP middleware: wraps requests
cmd/server/main.go - HTTP server → Embedded assets: serves assets
cmd/server/main.go - Route registry → Admin access: routes auth
internal/handlers/handler.go - Route registry → Room and joining: routes room
internal/handlers/handler.go - Route registry → Game and scoring: routes game
internal/handlers/handler.go - Route registry → Question management: routes questions
internal/handlers/handler.go - Route registry → Quiz library: routes quizzes
internal/handlers/handler.go - Route registry → Join QR code: routes QR
internal/handlers/handler.go - Room and joining → SQLite state: reads and writes
internal/handlers/room.go - Room and joining → WebSocket hub: broadcasts events
internal/handlers/room.go - Room and joining → Domain models: uses types
internal/handlers/room.go - Game and scoring → SQLite state: reads and writes
internal/handlers/game.go - Game and scoring → WebSocket hub: broadcasts events
internal/handlers/game.go - Game and scoring → Domain models: uses types
internal/handlers/game.go - Quiz library → SQLite state: manages quizzes
internal/handlers/quizzes.go - Quiz library → Domain models: uses types
internal/handlers/quizzes.go - WebSocket hub → Admin panel: sends events
README.md - WebSocket hub → Player app: sends events
README.md