Summary
Device config (~/.config/lazydeck/devices.toml) is per-user and local. Studios with shared QA labs of devkits want one source of truth for the device list rather than each engineer maintaining their own copy.
Problem
- No way for a team to share a single registry of paired devkits, their names/addresses, and metadata.
lazydeck serve is loopback-only, so there's no shared service a whole team or CI farm can point at.
Proposed direction (open to discussion)
- A device registry format/store that can live in a shared location (network path, git repo, or a small central service) instead of only
~/.config/lazydeck.
lazydeck serve gaining an option to bind beyond loopback for trusted-network use, gated behind explicit opt-in and the existing bearer-token auth (see #TBD auth issue for hardening that token model for multi-user use).
Why it matters
This is the biggest structural blocker to lazydeck being usable by a team rather than a single developer — everything else (auth, audit, RBAC) builds on top of having a shared registry to apply those controls to.
Summary
Device config (
~/.config/lazydeck/devices.toml) is per-user and local. Studios with shared QA labs of devkits want one source of truth for the device list rather than each engineer maintaining their own copy.Problem
lazydeck serveis loopback-only, so there's no shared service a whole team or CI farm can point at.Proposed direction (open to discussion)
~/.config/lazydeck.lazydeck servegaining an option to bind beyond loopback for trusted-network use, gated behind explicit opt-in and the existing bearer-token auth (see #TBD auth issue for hardening that token model for multi-user use).Why it matters
This is the biggest structural blocker to lazydeck being usable by a team rather than a single developer — everything else (auth, audit, RBAC) builds on top of having a shared registry to apply those controls to.