ops: persist livekit-server and camera fleet as systemd 24/7 units

This commit is contained in:
Hermes
2026-08-28 05:41:18 +00:00
parent 30b128bc9e
commit b5a2fe6440
4 changed files with 42 additions and 10 deletions
+9 -8
View File
@@ -82,18 +82,19 @@ lightweight high-pass + soft-clip DSP path so streams still work.
Until the 1 s window is full, hops use the DSP fallback so LiveKit is
not silent on startup.
## systemd (optional, not enabled)
## systemd (enabled, 24/7)
Two units, enabled for multi-user.target:
- `livekit-server.service` — `/usr/local/bin/livekit-server` + `deploy/livekit-server.yaml` (:7880)
- `livekit-cameras.service` — `run.py` (Requires livekit-server)
```bash
sudo cp deploy/livekit-cameras.service /etc/systemd/system/
sudo systemctl daemon-reload
# only if you want 24/7:
sudo systemctl enable --now livekit-cameras
systemctl status livekit-cameras livekit-server
journalctl -u livekit-cameras -f
systemctl restart livekit-cameras # pick up newly plugged cameras
```
Requires a LiveKit server already listening (this host uses
`/tmp/livekit-server --config /tmp/livekit-test.yaml` on :7880).
## Notes
- Video uses MJPG directly from the UVC interface (`ffmpeg -f v4l2