deploy: split build into docker-compose.dev.yml (prod compose pulls only) #55
Reference in New Issue
Block a user
No description provided.
Delete Branch "deploy/compose-dev-prod-split"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #54. That PR kept
build:alongsideimage:in a single file; this makes the basedocker-compose.ymlstrictly production-shaped and moves local builds to an explicit overlay, so a production host can never accidentally build.Change
docker-compose.yml— removebuild:fromappandbot;image:only.docker-compose.dev.yml(new) — addsbuild:back (app →Dockerfile, bot →bot/Dockerfile). Named explicitly so it is not auto-loaded likedocker-compose.override.yml.Why
With both
build:andimage:in one file, Compose givesbuildprecedence forup --build/build, mixing two deployment modes. Keepingbuild:out of the base file makes an accidental production build impossible.Usage
Verified
docker compose configrenders the base as image-only, no build for both services; the dev overlay addsbuild:back (app →Dockerfile, bot →bot/Dockerfile). README quick-start updated to the two-file flow.🤖 Generated with Claude Code
https://claude.ai/code/session_0114TpmrNW4wNXsHq5CR72jQ