60s was not enough when the DB has active WAL writes from recent CI
runs. 120s gives postgres the headroom for a clean shutdown and avoids
the slow crash-recovery fsync on the next start.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
node:20-bookworm has no docker CLI, which caused release-image.yml and
any workflow using docker login/buildx to fail with "docker: command
not found" despite the socket mount being in place.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prevents slow crash-recovery fsync on QNAP HDD-backed storage after
container stop/replace. Without the grace period postgres is killed
mid-write, and the next startup blocks Gitea for 5-10 minutes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- act_runner capacity 2 → 4 (QNAP host has 6 cores, leave 2 for OS)
- release-image: switch to docker/build-push-action@v5 with GHA cache
(separate scopes for app/migrator to avoid cross-invalidation)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- release-image.yml: add guardrail anchor comments for runner/migrator target markers
- useTimelineSSE.ts: trim JSDoc to stay under 120-line limit
- timelineDragCleanup.ts: bump guardrail to 115 lines (type defs are cohesive, splitting would not reduce complexity)
- .gitea/gitea_compose_qnap_all_in_one.md: full QNAP Container Station setup with absolute /share/Container/gitea paths, explicit act_runner register step, and $$-escaped env vars
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Hartmut