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>
27 lines
932 B
YAML
27 lines
932 B
YAML
# cogitator-02: an Apple Silicon Mac on the tailnet. Ansible manages it as
|
|
# phil; only tasks that set `become: true` use sudo.
|
|
ansible_python_interpreter: /usr/bin/python3
|
|
ansible_become_password: "{{ vault_cogitator02.become_password }}"
|
|
|
|
homebrew_taps:
|
|
- beeper/tap
|
|
homebrew_formulae:
|
|
- beeper/tap/bbctl
|
|
homebrew_casks:
|
|
- beeper
|
|
- claude-code
|
|
|
|
# Power settings (pmset, AC power). The Mac had `sleep 1` and only stayed up
|
|
# because BlueBubbles runs caffeinate; this keeps it up on its own.
|
|
mac_pmset:
|
|
sleep: 0 # never sleep
|
|
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
|