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>
1.9 KiB
1.9 KiB
mac
Manages cogitator-02, an Apple Silicon Mac on the tailnet (mac.yml,
PLAYBOOK=mac.yml bin/deploy).
- Homebrew (tag
homebrew): taps, formulae and casks listed ingroup_vars/mac/main.yml. Installs what's missing; never upgrades or removes. - SSH key (tag
ssh): your local~/.ssh/id_ed25519.pubin phil'sauthorized_keys. Other keys there are left alone. - Power (tag
power):mac_pmsetingroup_vars/mac/main.yml: never sleep, power back on after a power cut, wake on network. - Firewall (tag
firewall): macOS's application firewall on, with signed software allowed automatically (SSH, BlueBubbles, AirPlay, Tailscale), no stealth mode and no block-all. Any unsigned program that needs incoming connections has to be allowed explicitly, or the firewall silently blocks it. (Nothing needs that today.) - Hermes dashboard (tag
hermes-dashboard): a launchd service (local.hermes-dashboard) runninghermes dashboardon 127.0.0.1:9119, and Tailscale Serve publishing it athttps://cogitator-02.porgy-porgy.ts.net, reachable from the tailnet only. Login is usernameadminwith the password hash and signing secret fromvault_cogitator02, written into~/.hermes/.env(a plaintext password line there is removed, since it would override the hash). After setting up Serve, the play checks the dashboard demands a login through it; if not, it turns Serve off and fails.
Ansible logs in as phil. sudo needs phil's password, which is in the vault
as vault_cogitator02.become_password; only tasks with become: true use it.
phil deliberately doesn't get passwordless sudo, because Hermes Agent runs as
phil and takes commands over Telegram.
Not managed here: Hermes Agent itself (~/.hermes, a self-updating git
install on the stable channel, launchd agent ai.hermes.gateway), its other
settings, and the Tailscale app.