Files
ansible/group_vars/mac/main.yml
T
PhilandClaude Opus 5.5 eff53f2503 Mac: Hermes settings via hermes config, full pre-update backups
Adds a small hermes_settings map that Ansible checks with
`hermes config get` and fixes with `hermes config set`, leaving the rest
of config.yaml to Hermes (its updates migrate that file).

First setting: updates.pre_update_backup: full (was false), so every
`hermes update` zips ~/.hermes first. Rollback isn't supported once a new
version has written state.db, so the backup is the way back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 06:57:46 -07:00

32 lines
1.1 KiB
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
# Individual Hermes settings, set with `hermes config set`. The rest of
# ~/.hermes/config.yaml stays Hermes's own (its updates migrate that file).
hermes_settings:
updates.pre_update_backup: full # zip of ~/.hermes before every update