`hermes config get` writes "Config key not set" to stderr and Hermes's
default to stdout, so terminal.cwd: null looked set ("."), the play tried
to unset it again and `unset` failed on the missing key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The VM resize in a92d4c1 worked but left the VM stopped: a VM started from
an Ansible task is stopped when the task ends. Nothing started the VM at
login either, so after a reboot Hermes's sandbox stayed down.
- launchd job local.podman-machine runs `podman machine start` at login;
the resize now starts the VM through it and waits until it's running.
- Hermes setting changes also restart the dashboard, which keeps its own
copy of the settings (it kept logging the old /workspace cwd).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
ckulka/baikal is stuck on Baikal 0.10.1 (PHP 8.1). dschoepel/baikal is a
drop-in successor of its nginx variant (same volumes, UID 101) with
Baikal 0.13.0 on PHP 8.4. Upgrade tested on a copy of the data.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Compose deploys used the default pull policy (missing), so switching a
service to a tag that was already cached deployed a year-old image
(paperless-ngx and heyform :latest). module_defaults now sets pull: always
for every docker_compose_v2 task.
dockcheck pulls the image it updates, but then ran compose up for the
whole stack, which could recreate other containers in the stack from
cached images, including ones it excludes. OnlySpecific=true limits it to
the updated container.
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>
4.4 is end-of-life. Moved by mongodump/mongorestore into a new volume
(heyform_database7); the 4.4 volume stays for rollback.
The restore also fixes a data mix-up. From Nov 2024 the compose file set
MONGO_URI='mongodb://mongo:27017/heyform' in list form, so the quotes
became part of the value and HeyForm used a database literally named
"heyform'". The v3 upgrade (a1a79af) dropped the quotes, which switched
HeyForm to the old "heyform" database from the first week of setup, so
the real Repairs and Volunteer forms (91 submissions) disappeared. The new
volume holds "heyform'" restored as "heyform". Tested first with v3 on a
throwaway Mongo 7.0: both forms load.
Backups: ~/backups/heyform-mongo4.4-20261109 on the server (dump of both
databases + tar of the 4.4 volume).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gitea/gitea:1 stopped moving in August when Gitea renumbered to 28.0, and
1.27 gets no more fixes (28.0 fixed ~20 CVEs). Track :latest so the next
renumber can't freeze it again. The act_runner image was renamed to
gitea/runner; the old one stopped updating in April. The .runner
registration file and config format carry over unchanged.
v28 starts deleting Actions runs older than 400 days; set
RUN_RETENTION_DAYS=0 to keep the history.
Checked for this instance: ROOT_URL/SSH_DOMAIN set, no ALLOWED_HOST_LIST,
no webhooks or custom templates, one pull mirror from a public host.
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>
dockcheck runs as phil (docker group) and couldn't read
/opt/stacks/gokapi (0700 root), so the labelled gokapi container could
never be auto-updated. Paperless's root-only .env (2024 leftover, unused,
same values as docker-compose.env) made docker compose fail for phil.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Install dockcheck as a git clone in ~/.local/share/dockcheck with
AutoSelfUpdate (git pull also updates notify templates and urls.list);
no pinned versions. regctl is refreshed weekly by run_dockcheck.sh.
- Since dockcheck ~v0.7, OnlyLabel skips unlabelled containers entirely, so
they got no update notices. run_dockcheck.sh now runs twice: update
labelled containers quietly, then check everything and notify once.
- Running dockcheck.sh by hand now checks everything and changes nothing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Pin dockcheck (v0.8.3) and regctl (v0.11.7) and re-download on version
bumps; get_url never replaced existing files, and dockcheck never updates
regctl itself (server had regctl v0.8.3 from June 2025)
- New options: DaysOld=3, BackupForDays=7 (rollback), MaxAsync=10,
MonoMode for the log, PrintReleaseURL with upstream urls.list
- Drop authentik-postgresql-1 from Exclude (container is gone)
- Wrapper logged exit code 0 always ($? read after $(date)); fixed
- Rotate /var/log/dockcheck/dockcheck.log weekly
- Remove stale ~/.local/bin/notify_v2.sh
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>