Migration 023 adds notes.title/summary (no prod notes start with a heading,
so no files are rewritten). Backup: /data/backup-pre-v2.16.0.db and
/data/backup-pre-v2.16.0-files.tgz in the starpunk-data volume.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the starpunk-mcp container (same image, uvicorn :8001, shared env via
anchor, BACKGROUND_WORKERS_ENABLED=false, socket healthcheck) and route
/mcp and /.well-known/oauth-protected-resource to it in Caddy. Bump
starpunk_version to v2.15.0 (needs the v2.15.0 tag built first).
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>