Hermes has no auto-update for itself, and /update from Telegram can leave a launchd gateway offline. Instead, a no-agent Hermes cron job runs `hermes update --check` on Mondays at 09:07 and messages Telegram only when a new stable release is out (a failing check sends an error alert). Adds hermes_cron_jobs (scripts in files/hermes-scripts/, copied to ~/.hermes/scripts/; jobs created when missing) so the deal checker can follow the same pattern. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5 KiB
2.5 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. - Hermes settings (tag
hermes-settings): the individual keys inhermes_settings(group_vars/mac/main.yml), checked withhermes config getand fixed withhermes config set. Today: a full backup of~/.hermesbefore everyhermes update. - Hermes cron jobs (tag
hermes-cron):hermes_cron_jobsingroup_vars/mac/main.yml, with their scripts fromfiles/hermes-scripts/copied to~/.hermes/scripts/. Missing jobs are created; existing ones are left as they are. Today:hermes-update-notice, which messages you on Telegram on Mondays only when a new stable Hermes release is out.
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.