The TUI is now a TypeScript/opentui app in tui/ rather than Bubble Tea.
opentui is a Zig core with TypeScript bindings and no Go bindings, so this half
of the tool can't live in the Go binary; it compiles with Bun into a sibling
executable (rtsp-streamer-tui) that `rtsp-streamer tui` execs.
Everything that isn't presentation stays in Go, reached over three JSON
commands. The configurator holds no credentials and never writes the config
itself:
config export the config, plus limits like max_tiles
config apply (stdin) merge cameras/layouts/active_layout, validate, save
atomically, reload the daemon
discover --json Protect discovery, writing nothing
Two properties of that split are deliberate:
- The controller password never crosses the bridge. It's json:"-" on the way
out, and apply only merges the three keys the TUI edits, so it can't be
clobbered on the way back in either.
- apply re-reads the file before merging, so an editor left open for an hour can
no longer overwrite a `views import`, a `layout set`, or a hand edit made in
the meantime.
Discovery is previewable as a result: `discover --json` writes nothing, the
merge happens in the TUI, and nothing reaches disk until you save. Only
--enable-rtsp has a side effect, and it's on the controller.
Config structs gain json tags mirroring their yaml ones so the config
round-trips through the bridge under the same key names it has on disk, and
maxGridDim moves to config.MaxGridDim so the CLI and both configurators enforce
one ceiling. The write path is byte-for-byte identical to `layout set`, checked
against a copy of a live config.
Visible change: the grid editor draws real bordered boxes, so a spanning tile is
one box instead of an origin cell plus "·" continuation marks, and the
header-offset arithmetic in mouse.go is gone — the framework hit-tests list
rows. Keybindings, the lipgloss palette and the screen flow are carried over
unchanged; S now saves from anywhere.
The Bubble Tea version stays as `tui --legacy`. It's compiled into the Go binary
and needs no Bun, and on a headless Pi the TUI is the only config UI there is,
so a fallback is worth its weight. The cost of the new one is size: ~120 MB
against ~13 MB, since Bun embeds its runtime and opentui's native library.
Tests: 67 bun tests drive the real (in-memory) opentui renderer, including mouse
click and drag, plus tsc --noEmit. `make test-tui` runs both, and
scripts/preview.ts dumps every screen as text without needing a terminal.
Three bugs found during the port are documented in tui/README.md, since none are
apparent from the code: overlapping cell borders render as ┌ where a lattice
needs ┬; a drag dies after the first resize if the tree is rebuilt, because the
renderer captures the press-target renderable; and a rebuilt box has no computed
layout until the next frame, so its screenX reads 0.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two related gaps on the headless kiosk: no way to restart the wall short
of a full reboot, and no way to see why a stream keeps flapping (the
daemon's stderr goes to sway on tty1, and mpv's stderr was discarded).
Restart in place:
- `rtsp-streamer restart` sends a control-socket command; the daemon
tears down its mpv children and syscall.Exec's the on-disk binary.
Same PID, same parent (sway), same env — keeps WAYLAND_DISPLAY/
SWAYSOCK and comes back up on the new binary, no reboot. Handles the
os.Executable() "(deleted)" sentinel from make install's rename.
- sway config now launches the daemon in a relaunch loop, so a crash (or
the restart) auto-recovers instead of leaving a black screen.
- `make deploy` now does `install` + `restart` instead of restarting
getty@tty1 (which left stale duplicate sessions and forced reboots).
Retrievable logs:
- New internal/logbuf ring; the daemon tees slog output into it and
serves the tail over the socket via `rtsp-streamer logs [-n N]` —
readable over SSH, no file wrangling, no reboot.
- Capture the tail of each mpv's stderr and log its last line when the
process exits, so "mpv exited, will restart" now carries the reason
(connection refused, unsupported codec, 401, ...). This is the
diagnostic for a single tile going unhealthy repeatedly.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Skip stream restarts when a reload resolves to the identical wall
(same URLs, tile geometry, player settings) — saving an unrelated
config edit no longer blanks the screen.
- Replace per-tile placement polling (a swaymsg fork per tile per second,
plus 150ms get_tree polling per tile at startup) with one shared loop:
a single get_tree snapshot per tick, re-placing only drifted windows,
relaxing to a 2s tick once settled.
- Mute streams by default (--no-audio) to skip an audio decoder per
stream; opt back in with player.audio: true.
- Graceful, parallel mpv teardown via cmd.Cancel/WaitDelay, fixing the
double-Wait race between Stop and Supervise and cutting worst-case
layout switches from ~2s x N streams to ~2s total.
- status: probe mpv IPC outside the daemon mutex so a slow probe can't
block layout switches.
- View sync: reuse the Protect session across ticks (re-login only on
expiry) and pick up view_refresh_seconds changes without a restart.
- Health strikes keyed by player, not slot, so they never carry across
layout switches; prune stale entries.
- New `rtsp-streamer reload` CLI; fix dead sort in `layout ls`; back off
on persistent control-socket accept errors; fsync config before the
atomic rename (SD-card power-cut safety); bump IPC client deadline;
gofmt stragglers.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
views ls/dump/import copy a Protect live view (cameras + grid) into a
layout; grid inferred from slot count (asymmetric presets TBD, see
views dump). Imported layouts link back via protect_view.
Daemon re-syncs the active linked view every view_refresh_seconds (0=
off), so Protect-side edits appear on the wall. Needs the controller
password at runtime; off by default keeps the wall credential-free.
Shared viewmap package used by CLI and daemon.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ldflags inject version, commit, and build date; a version subcommand
also reports go version and platform. Ends the which-binary-is-this
guessing after deploys.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
