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>
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>
The server now runs Debian 13.7. systemd 257's ssh generator logs a
harmless AF_VSOCK error on netcup VMs, so the common role masks it.
The plan file now records how the upgrade went and what's left.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Debian 13 drops apt-key and software-properties-common, so the old tasks
would fail after the upgrade. The key now lives in /etc/apt/keyrings
(same fingerprint, 9DC8...CD88), the repo is a deb822 file whose release
name follows the installed Debian, and the old .list file is removed.
The apt tasks get a docker_apt tag so they can be deployed on their own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Browsers will use HTTPS for each site for a year. includeSubDomains is
left off so hosts not served by this Caddy are unaffected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v0.1.0 (Feb 2025) has dozens of published security advisories fixed in
v3. Tested against a copy of the database first; forms load unchanged.
v3 listens on 9157, keeps uploads under packages/server, and uses Redis 8
commands, so KeyDB is replaced by redis:8-alpine. The homepage URL is now
https (v3's CORS allowlist is built from it), Caddy is the trusted proxy,
public sign-up is off, and integration credentials get their own key.
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>
v3 can only be reached from 2.20.15, so stop tracking :latest. Also set
the two settings v3 needs from us: trust Caddy as the proxy (v3's login
rate limiting), and keep rejecting duplicate documents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>