How kurtreonal/iot-dashboard works
Stack Moko Baby combines a player-facing QR registration, FIFO queue, physical-cabinet game and result/leaderboard flow with an operator dashboard. The React app routes users and manages API state; FastAPI owns authorization and game operations over MariaDB. The dashboard also provides analytics and Stack Intelligence, including private admin memory and review/export of sanitized routing examples. Arrows cite shown calls or README claims; undocumented subsystem wiring is omitted where source excerpts do not establish it.
Main entry points: main.py API routes · assistant.py Intent and answers · App.jsx App routing · AppContext.jsx Application state
Components 22
Player game flow
- App routing
frontend/src/App.jsx - QR registration
frontend/src/pages/Registration.jsx - Player ticket
frontend/src/pages/Ticket.jsx - Leaderboard
frontend/src/pages/Leaderboard.jsx
Operator dashboard
- Analytics
backend/app/analytics.py - Admin dashboard
frontend/src/App.jsx
Backend services
- Application state
frontend/src/state/AppContext.jsx - API client
frontend/src/state/api.js - API routes
backend/app/main.py - Session security
backend/app/security.py - MariaDB persistence
backend/app/database.py - Queue and results
backend/app/game.py
Stack Intelligence
- Assistant interface
frontend/src/components/AdminAssistant.jsx - Assistant state
frontend/src/state/AssistantContext.jsx - Intent and answers
backend/app/assistant.py - Knowledge grounding
backend/app/assistant_knowledge.py - Admin memory
backend/app/assistant_memory.py - Training review
backend/app/assistant_training.py - Routing examples
backend/app/assistant_interactions.py
Other components
- Players
- Physical cabinet
- Local Ollama
Connections 25
- Players → App routing: use
- App routing → QR registration: routes to
frontend/src/App.jsx - App routing → Player ticket: routes to
frontend/src/App.jsx - App routing → Leaderboard: routes to
frontend/src/App.jsx - QR registration → Application state: registers through
frontend/src/pages/Registration.jsx - Player ticket → Application state: reads state
frontend/src/pages/Ticket.jsx - Leaderboard → API client: loads rankings
frontend/src/pages/Leaderboard.jsx - Application state → API client: calls
frontend/src/state/AppContext.jsx - API client → API routes: HTTP requests
frontend/src/state/api.js - API routes → Session security: authorizes
backend/app/main.py - API routes → MariaDB persistence: queries
backend/app/main.py - API routes → Queue and results: delegates game actions
backend/app/main.py - Physical cabinet → API routes: submits results
- Admin dashboard → Application state: uses state
frontend/src/App.jsx - API routes → Analytics: collects metrics
backend/app/main.py - Assistant interface → Assistant state: uses state
frontend/src/components/AdminAssistant.jsx - Assistant state → API client: calls assistant endpoints
frontend/src/state/AssistantContext.jsx - API routes → Intent and answers: dispatches assistant requests
backend/app/main.py - Intent and answers → Analytics: reads analytics
backend/app/assistant.py - Intent and answers → Knowledge grounding: uses knowledge
backend/app/assistant.py - Intent and answers → Admin memory: loads and saves
backend/app/assistant.py - Intent and answers → Local Ollama: uses local model
- Assistant interface → Training review: reviews examples
- Training review → Routing examples: uses routing corpus
backend/app/assistant_training.py - Training review → MariaDB persistence: stores and exports
backend/app/assistant_training.py