How tronbyt/server works
Tronbyt Server is a self-hosted application manager and display service for Tronbyt-compatible devices. The principal workflow is: a user signs in, adds a device, discovers or configures an app, and the device retrieves rendered images for display. The repository also supports firmware generation, device APIs, repository-backed apps, legacy migration, and monitoring. The README documents the product workflow and capabilities; several internal connections are shown as unverified because the relevant handler and orchestration source was not excerpted.
Main entry points: server.go HTTP server · handlers_app.go App management · models.go Domain models · manager.js Web interface
Components 21
Access and UI
- Web interface
web/static/js/manager.js - Authentication
internal/server/auth.go - User management
internal/server/handlers_user.go - HTTP server
internal/server/server.go - Theme controls
web/static/js/theme.js
Apps and Rendering
- App management
internal/server/handlers_app.go - App catalog
internal/apps/apps.go - App repositories
internal/gitutils/git.go - Pixlet rendering
internal/renderer/renderer.go - Render cache
internal/pixletcache/cache.go
Devices and Firmware
- Device management
internal/server/handlers_device.go - Device API
internal/server/handlers_api.go - Device endpoints
internal/server/handlers_device_api.go - Firmware generation
internal/firmware/firmware.go
Persistence and Migration
- Domain models
internal/data/models.go - Database
internal/data/database.go - Legacy migration
internal/legacy/converter.go
Operations
- Metrics
internal/server/metrics.go - Live updates
internal/sync/broadcaster.go
Other components
- User
- Display client
Connections 23
- User → Web interface: manages devices
README.md - Web interface → Authentication: signs in
- Web interface → App management: configures apps
- Web interface → Device management: adds device
README.md - Display client → Device API: requests images
README.md - HTTP server → Authentication: routes requests
- HTTP server → User management: routes requests
- HTTP server → App management: routes requests
- HTTP server → Device management: routes requests
- HTTP server → Device endpoints: routes requests
- App management → App catalog: lists apps
- App management → Pixlet rendering: renders preview
- Pixlet rendering → Render cache: uses cache
- App repositories → App catalog: provides repository apps
- Device management → Firmware generation: generates firmware
README.md - Device API → Domain models: reads and updates
- App management → Domain models: reads and updates
- Device management → Domain models: reads and updates
- Database → Domain models: stores records
- Legacy migration → Domain models: converts records
internal/legacy/converter.go - HTTP server → Metrics: exposes metrics
README.md - HTTP server → Live updates: publishes updates
- User → Theme controls: customizes display