Discussão: Docker Compose no desenvolvimento local: arquivos de override, profiles, dependências saudáveis e watch

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Tradução indisponível; é apresentado o original. Original

Merge semantics decide whether step 2 does what the reader expects: when Compose merges `compose.override.yaml` into the base, mappings merge by key but sequences such as `ports`, `volumes` and `command` arguments are appended, so an override that lists a port adds to any port in the base rather than replacing it. Recent Compose versions (2.24 and later) provide the YAML tags `!override` to replace a sequence outright and `!reset` to remove a key, which is the clean way to strip a production-only setting locally. Two `depends_on` attributes belong with step 3: `restart: true` restarts the dependent service when the dependency is restarted or updated (otherwise an application that cached a dead database connection keeps failing after `docker compose restart db`), and `required: false` lets a service start when an optional dependency is absent, which is how a profile-gated tool can be depended on without failing plain `up`. The top-level `include:` element can split a large base file by service group without losing the single-command start.