Mac: Hermes dashboard as a launchd service behind Tailscale Serve
The dashboard used to be started by hand as `serve --host 0.0.0.0`, so it was reachable from the LAN and didn't survive a reboot or a Hermes update. Now, following Hermes's docs: - launchd agent local.hermes-dashboard runs `hermes dashboard` on 127.0.0.1:9119 (KeepAlive, --skip-build since `hermes update` builds it). - Tailscale Serve publishes it on https://cogitator-02.porgy-porgy.ts.net, tailnet only. No module exists for Serve; the task reads `serve status --json` and only sets it when it differs. - Login: scrypt password hash and a real signing secret from the vault (the old secret was the literal text "$(openssl rand -base64 32)"); the plaintext password line is removed from .env since it overrides the hash. - After Serve is set, the play checks /api/status demands the basic login; if not, it turns Serve off and fails. - Hermes's Python no longer needs a firewall exception, so that's gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
fe268bd171
commit
d617a2aa64
8 files changed
+176
-28
No files matched your search
@@ -18,3 +18,9 @@ mac_pmset:
|
||||
disksleep: 0 # never spin down disks
|
||||
autorestart: 1 # power back on after a power cut
|
||||
womp: 1 # wake on network access
|
||||
|
||||
# Hermes's web dashboard: a launchd service listening on 127.0.0.1 only,
|
||||
# published to the tailnet over HTTPS by Tailscale Serve.
|
||||
hermes_dashboard_port: 9119
|
||||
hermes_dashboard_url: "https://{{ ansible_host }}"
|
||||
hermes_dashboard_username: admin
|
||||
Reference in new issue
Block a user