A cross-platform bridge for forwarding game telemetry data via UDP and OSC, with a modern React dashboard for configuration and live monitoring.
- Real-time telemetry forwarding via UDP and OSC
- Web dashboard for configuration, live data, and service control
- Packet forwarding and OSC address mapping
- Service restart endpoints for hot-reloading without full restart
.
├── backend/ # Go backend (API, UDP/OSC, static file server)
│ ├── main.go
│ ├── config.go
│ ├── ...
│ └── dist/ # Built frontend assets (output from frontend build)
├── frontend/ # React + TypeScript + Vite frontend
│ ├── src/
│ ├── index.html
│ └── ...
├── package.json
└── README.md
-
Delete old frontend build (recommended before rebuilding):
rmdir /s /q backend\dist -
Build the frontend (only if changes were made):
cd frontend npm install npm run build cd ..
This outputs static files to
backend/dist. -
Change the version:
- Update the
Versionvariable inbackend/main.goas needed. - Optionally update the version in
frontend/package.json.
- Update the
-
Build the backend application:
cd backend go build -o f1-telem-bridge.exe cd ..
The resulting binary will be
backend/f1-telem-bridge.exe.
backend\f1-telem-bridge.exe- The dashboard will open automatically at http://localhost:1337.
-
Start the frontend dev server:
cd frontend npm run dev -
Run the backend (serves API only):
cd backend go run .
- Visit the frontend at the URL shown by Vite (usually http://localhost:5173).
- The backend API will be available at http://localhost:1337.
You can restart UDP, OSC, or all services via the dashboard or by calling:
POST /api/restart/udpPOST /api/restart/oscPOST /api/restart/all
- Config files and logs are stored in your user config directory (e.g.
%APPDATA%\f1-telem-bridgeon Windows). - Logs are written to
app.log.
MIT © 2025 Adam Ashdown