fix(devcontainer): name the dev stack apart from the deploy stack #9

Merged

TimCane merged 1 commit from fix/devcontainer-project-name into main

2026-07-19 15:36:17 +01:00

TimCane commented

2026-07-19 15:35:13 +01:00

(Migrated from github.com)

Summary

Both compose files declared name: mealplan-mcp. Bringing up the deploy stack reconciled against the running devcontainer instead of starting alongside it - it stopped the dev database and detached it from its network
The devcontainer stack is now mealplan-mcp-dev; the deploy stack keeps the project name

Found while running the first live crawl. Recovering needed a docker network connect, which is not something to discover twice.

Test plan

Takes effect on the next devcontainer rebuild; until then the deploy stack needs an explicit -p to avoid the still-running dev containers
Verified 172.28.0.0/16 (deploy) does not overlap the dev network's 172.27.0.0/16

## Summary - Both compose files declared `name: mealplan-mcp`. Bringing up the deploy stack reconciled against the *running devcontainer* instead of starting alongside it - it stopped the dev database and detached it from its network - The devcontainer stack is now `mealplan-mcp-dev`; the deploy stack keeps the project name Found while running the first live crawl. Recovering needed a `docker network connect`, which is not something to discover twice. ## Test plan - Takes effect on the next devcontainer rebuild; until then the deploy stack needs an explicit `-p` to avoid the still-running dev containers - Verified `172.28.0.0/16` (deploy) does not overlap the dev network's `172.27.0.0/16`