Via hermes_settings (now compared structurally, with null = unset, and a
gateway restart on change):
- timezone America/Denver (was unset)
- auth.adopt_external_logins false: never borrow Claude Code's login
- terminal.cwd unset: stops the /workspace warnings (#140527)
- agent.disabled_toolsets [kanban]: unused, 25 KB of tool schema per call
- skills.write_approval true
- approvals.deny: force-push, curl|sh, dd to devices (docs' examples)
- streaming.enabled true, stt.local.model small
- terminal.container_memory 3072, inside a 4 GB Podman VM (was 2 GB VM
with a 5 GB container limit), set by a new podman task
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
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>
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>
- pmset: never sleep, no disk sleep, restart after a power cut, wake on
network. The Mac had sleep 1 and only stayed up because BlueBubbles runs
caffeinate.
- Application firewall on, keeping signed software allowed automatically,
stealth and block-all off. Hermes's ad hoc signed Python (dashboard on
9119) is allowed explicitly, since an unattended Mac blocks unsigned
programs silently.
- Local id_ed25519.pub in phil's authorized_keys (already there).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cogitator-02 is an Apple Silicon Mac on the tailnet running Hermes Agent.
It gets a `mac` group and mac.yml, kept apart from site.yml so it never
runs with the server's deploys (PLAYBOOK=mac.yml bin/deploy).
The mac role starts by recording the Homebrew taps, formulae and casks
already installed (present only, never upgrades or removes), so the first
run changes nothing.
No passwordless sudo on the Mac: Hermes runs as phil and takes commands
over Telegram. Ansible's sudo password is vault_cogitator02.become_password
and only tasks with become: true use it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 1.7 -> 1.22 upgrade is done; the app gets the dockcheck label.
Redis and Postgres stay excluded in dockcheck.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.17.0 background jobs drained cleanly. 1.18.1 (skipping 1.18.0, which
needed the hotfix) converts Areas to Places and re-detects visits across
the whole history; the changes can't be rolled back, so a fresh dump was
taken first (~/backups/dawarich-1.17.0-20261109). Redis goes to 8 as in
upstream's compose since 1.18.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follows the 1.17.0 upgrade notes and upstream compose: the separate
dawarich_sidekiq service is gone (removed on the host before deploying),
the app runs Sidekiq embedded (SIDEKIQ_EMBEDDED=true, WEB_CONCURRENCY=0,
BACKGROUND_PROCESSING_CONCURRENCY=2), gets stop_grace_period 60s, and the
limits match upstream (1 CPU, 4G).
Fresh dump before this step: ~/backups/dawarich-1.16.0-20261109.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.14.5 background jobs fully drained (checked queues, scheduled and retry
sets, and job logs). 1.16.0 is the last release with the separate sidekiq
container and merges duplicate legacy points.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both earlier failures had one cause: the host still had old images cached
under the :latest tag (paperless-ngx from 2025-09, i.e. 2.x; heyform from
2025-02, i.e. v2), and the compose task only pulls missing images. So the
switch to :latest started year-old code. Pulled the real :latest images on
the host. Paperless 3.4.2 has no pending migrations on this database
(checked on a copy), and HeyForm v3.0.6 listens on 9157 as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.10.3 migrated cleanly and its background jobs have drained. 1.14.5
fixes the registration bypass (GHSA-x483-3xv3-vp52) and runs the
1.11-1.14 track/visit recalculation and point backfill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- HeyForm v3.0.6 changed the default listen port from 9157 to 8000, so
Caddy got 502s. Set APP_LISTEN_PORT=9157 explicitly.
- Paperless 3.4.2 fails its migration check on this database
(InconsistentMigrationHistory, squashed 1022..1036). Rolled back to 3.4.1
until that is investigated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
First stop is 1.10.3 (drops the legacy lat/lon columns with the 1.10.2
lock fix). Next stops: 1.14.5 (security fix), 1.16.0, 1.17.0 (sidekiq
merged into the app), 1.18.1, 1.22.0, then back to latest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pinned versions never got updates, because dockcheck only notices a new
image under the same tag.
- paperless-ngx: 3.4.1 -> latest (stable only; beta/dev have own tags)
- paperless redis: 7 -> 8-alpine (reads Redis 7 data as-is)
- gotenberg: 8.39.0 -> 8 (9 changed the API Paperless calls)
- tika: 3.3.1.0 -> 3.3.3.0 (no floating 3.x tag; Tika 4 breaks Paperless)
- heyform: v3.0.5 -> latest (only moved by v* release tags)
- add mag37.dockcheck.update to all of the above
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pass the Threads token (vault_starpunk.threads_access_token, Meta app
"starpunk") and username philskents. StarPunk refreshes the token daily
and keeps the current one in /data/threads_token.json.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
StarPunk 2.1.0 copies new notes to GoToSocial and keeps edits and
deletes in step. Token for the app "StarPunk crossposting" (scopes
write:statuses write:media) is in vault_starpunk.gotosocial_token; the
container reaches social. through Caddy (hairpin).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.20.15 has run its migrations, so this is the supported jump to v3.
Search moves to Tantivy and is rebuilt on first start.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>