service_manager: LiveKit credential auto-bootstrap (hero_collab) #93

New issue

Open

opened 2026-05-07 19:11:42 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-07 19:11:42 +00:00

Owner

Tracked from #90.

The upstream nu module service_collab.nu does an auto-bootstrap of LiveKit creds on a dev box: starts hero_livekit if not already running, reads ~/hero/var/hero_livekit/runtime.json for URL/key, writes the API secret to ~/hero/cfg/livekit.secret (mode 0600), then passes paths to hero_collab_server env.

The v2 hero_collab::start impl (PR #92) only forwards LIVEKIT_URL / LIVEKIT_API_KEY / LIVEKIT_API_SECRET_FILE from the manager's caller env. It does NOT auto-start hero_livekit or read runtime.json.

Fix: extend hero_collab::start (or a helper in service_manager::lib) to mirror the nu module's resolution ladder: explicit env → runtime.json → start hero_livekit → re-read.

Code-not-data design means this is just adding logic inline in the service file; no schema extension needed.

Limitation: doc comment in crates/hero_router/src/service_manager/services/hero_collab.rs.

Tracked from #90. The upstream nu module `service_collab.nu` does an auto-bootstrap of LiveKit creds on a dev box: starts `hero_livekit` if not already running, reads `~/hero/var/hero_livekit/runtime.json` for URL/key, writes the API secret to `~/hero/cfg/livekit.secret` (mode 0600), then passes paths to `hero_collab_server` env. The v2 `hero_collab::start` impl (PR #92) only forwards `LIVEKIT_URL` / `LIVEKIT_API_KEY` / `LIVEKIT_API_SECRET_FILE` from the manager's caller env. It does NOT auto-start hero_livekit or read runtime.json. **Fix**: extend `hero_collab::start` (or a helper in `service_manager::lib`) to mirror the nu module's resolution ladder: explicit env → runtime.json → start hero_livekit → re-read. Code-not-data design means this is just adding logic inline in the service file; no schema extension needed. `Limitation:` doc comment in `crates/hero_router/src/service_manager/services/hero_collab.rs`.