Multi-host phase 1: API tokens, auto TLS with pinned fingerprints, hub-side node manager + reverse proxy (WebSockets included), machine switcher in the rail, Machines page

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Mitchell-Johnson
2026-09-18 11:35:29 -07:00
co-authored by Claude Fable 5.1
parent fc42675e9f
commit 7dcdb5dc98
15 changed files with 960 additions and 56 deletions
+9
View File
@@ -24,5 +24,14 @@ sudo systemctl start hamlab # listens on 127.0.0.1:8100 by default; set "lis
Terminals run as the user the service runs as, with that user's login shell.
## Managing several machines
Install Ham Lab on each host. On the ones the hub should reach, add `"tls": "auto"` and a
LAN `listen` address to `config.json` (a self-signed certificate is generated on first
start). Then on the hub, open **Machines**, enter a name, the address
(`https://host:8100`) and that machine's Ham Lab password once. The hub pins the
certificate, keeps an access token, and every tab works against the chosen machine
through the switcher at the top of the rail.
- On `core` it is public at `https://hamlab.bigham.dev` behind Nginx Proxy Manager.
- Installable as a PWA.