How bagaart/alpha works
This is a browser-based scanner and tag map: the page loads map metadata and scanner records, fetches the map SVG, then renders selectable scanners and live tag positions with details in a sidebar. The backend serves the frontend and HTTP data, and broadcasts simulated tag updates over WebSocket. The map asset is referenced by the backend but is absent from the supplied tree; relationships are limited to those shown in the excerpts.
Main entry points: main.js App initializer · main.py HTTP and WebSocket API · tags.js Live tag markers · sidebar.js Entity sidebar
Components 10
Backend services
- HTTP and WebSocket API
backend/main.py - Data models
backend/models.py
Browser application
- App initializer
frontend/js/main.js - API client
frontend/js/api.js - Map loader
frontend/js/map.js - Scanner rendering
frontend/js/scanners.js - Live tag markers
frontend/js/tags.js - Entity sidebar
frontend/js/sidebar.js
Application data
- Scanner catalog
backend/data/scanners.json
Other components
- Map user
Connections 12
- Map user → App initializer: opens map
frontend/js/main.js - App initializer → API client: requests data
frontend/js/main.js - API client → HTTP and WebSocket API: fetches endpoints
frontend/js/api.js - HTTP and WebSocket API → Scanner catalog: loads records
backend/main.py - HTTP and WebSocket API → Data models: validates data
backend/main.py - App initializer → Map loader: loads SVG
frontend/js/main.js - App initializer → Scanner rendering: renders scanners
frontend/js/main.js - App initializer → Live tag markers: connects updates
frontend/js/main.js - HTTP and WebSocket API → Live tag markers: streams tag updates
backend/main.py - App initializer → Entity sidebar: shows selection
frontend/js/main.js - Scanner rendering → Entity sidebar: selects scanner
frontend/js/main.js - Live tag markers → Entity sidebar: selects tag
frontend/js/main.js