merge queue: merged #94: feat: allow a local production image without GHCR

Draft
ME
3h ago
+42-5

[!NOTE]
This is a merge queue draft opened by Mergify. Its pull request has merged, and nobody needs to act on it.
Mergify opened it for batch petite-persillade-w89wpt of the default queue, to test #94 before it merged into main.

🎉 What landed

Mergify merged its pull request into main, then closed this draft:

  • #94 feat: allow a local production image without GHCR (ashcoft), as 9b3fad4

This draft's code was built in this order:

  1. main at 0d35f7a
  2. #94, the pull request of this batch
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 0d35f7a7d748991f3b3ec276965d6ddf6aebf3a2
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 94
    scopes: []
queue_base_sha: 0d35f7a7d748991f3b3ec276965d6ddf6aebf3a2
scopes: []
...

Required conditions of queue rule default for merge

No extra conditions.

Required conditions to stay in the queue

None


Summary by cubic

Lets production Docker deployments use a locally built image instead of always pulling from GHCR, which helps hosts that cannot reach the registry.

  • Makes the production pull policy configurable with POL_PULL_POLICY (default always; set never for a locally built image).
  • Unifies the image tag across both compose files via POL_VERSION so local builds carry the tag production expects.
  • Documents a docker save/load backup workflow so a removed container does not force a GHCR login.
  • Excludes image archive backups from the Docker build context and updates .env.example.

RetriggerView in GreptileConfidence Score: 4/5

The PR appears safe to merge, with non-blocking fixes recommended for the image-backup instructions.

Fix All in CodexFindings

  1. P2 Backup chooses the wrong image â–¶
  2. P2 Failed backup looks successful â–¶
Fix with agent prompt
### Issue 1
readme.md:299
The backup command parses `.env` differently from Compose. For example, `POL_VERSION="1.4.0"` works in Compose, but this command keeps the quote characters, so `docker save` receives an invalid image name. It also overwrites any exported `POL_VERSION`, which can select a different image from the one Compose uses.

Ask Compose for the resolved application image instead. Apply the same fix to the repeated backup command in Operations.

### Issue 2
readme.md:300-301
If `docker save` fails because the image is missing or Docker is unavailable, `gzip` can still accept the empty input, write an empty compressed archive, and report success. The command can also overwrite an earlier usable backup.

Enable `pipefail` and replace the backup only after the whole pipeline succeeds. Fix the repeated Operations example too.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR lets production use a locally built or restored application image.

  • Production can run a local image under the shared version tag.

Reviews (1) · Last reviewed commit: "Merge of PR 94" · Reviewed by Greptile