feat: users, roles and per-area permissions, production demo image

The controller checks every route against the signed-in user's role, with
levels none, view, control and edit per area. Guests get the permissions
of a built-in guest role. Auth stays off until the first user exists;
LED_ADMIN_USER and LED_ADMIN_PASSWORD create the first admin.

Sessions are cookies, passwords are PBKDF2-SHA256, and logins lock per
username after five failures. The simulator's WebSocket checks the view
permission at handshake and per frame; /ws needs devices control. The web
UI gets a sign-in button, a sign-in prompt on refused changes, and a users
and roles screen.

Also: the device build gets the bridge include path and forward type it
was missing, Dockerfile.sim runs non-root, and Dockerfile.prod with
docker-compose.prod.yml runs the controller on an internal network behind
Caddy for HTTPS.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
This commit is contained in:
jimmyandClaude Haiku 5.5 committed 2026-11-17 00:29:04 +13:00
1 parent 02440be55d
commit f0615dc1b7
26 files changed
+2116 -23

No files matched your search

+6
View File
@@ -75,12 +75,18 @@ def restore_db(request):
yield
return
client = request.getfixturevalue("c")
if client.get("/auth").json().get("enabled"):
# test_auth.py turned sign-in on: the snapshot needs editor rights, so the data is left as it is
yield
return
snapshot = {}
for name in COLLECTIONS:
resp = client.get(f"/db/{name}")
resp.raise_for_status()
snapshot[name] = resp.json()
yield snapshot
if client.get("/auth").json().get("enabled"):
return # test_auth.py switched sign-in on during the run: it cannot be restored without an admin
failed = []
for name, data in snapshot.items():
resp = client.put(f"/db/{name}", json=data)