Skip to content

Docs: run a released image via COMPOSE_FILE; warn that -f prod alone reverts - #78

Merged
WittsEnd2 merged 1 commit into
mainfrom
docs-released-image-compose-file
Oct 27, 2026
Merged

WittsEnd2 merged 1 commit into
mainfrom
docs-released-image-compose-file

Conversation

@WittsEnd2

Copy link
Copy Markdown
Member

Found while moving production to the v1.0.0 image.

  • Running a released image now sets COMPOSE_FILE=docker-compose.prod.yml:docker-compose.release.yml plus LAB_PLAYGROUND_VERSION in .env (as DEPLOY-FROM-RELEASE.md already does), so a plain docker compose uses the image for every command. Upgrades and rollbacks are one value change.
  • Warns about the pitfall. An explicit -f docker-compose.prod.yml replaces COMPOSE_FILE, so the app service gets its build: back. The previous text said only --build reverts, but a plain up -d also silently switches to any locally built image still on the host. Verified on a real host: docker compose config --images gives the GHCR image, while docker compose -f docker-compose.prod.yml config --images gives the local build. exec, logs and the backup script's exec db are safe.

Docs only. Release/doc tests pass (103).

…reverts

Found while moving production to the v1.0.0 image: an explicit
-f docker-compose.prod.yml replaces COMPOSE_FILE, so the app service gets
its build back and a plain up -d silently switches to any locally built
image still on the host (verified with docker compose config --images).

Co-Authored-By: Claude <noreply@anthropic.com>
@WittsEnd2
WittsEnd2 requested a review from a team as a code owner October 27, 2026 21:00
@WittsEnd2
WittsEnd2 merged commit bd75a88 into main Oct 27, 2026
3 checks passed
@WittsEnd2
WittsEnd2 deleted the docs-released-image-compose-file branch October 27, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant