There was an error while loading. Please reload this page.
Correct what local DNS actually does Five pages said containers can't reach each other by name and that local DNS only helps this Mac. Both wrong once a default domain is configured: containers resolve each other as db.test and as bare db, verified with an HTTP 200 between two containers by bare name. Also records the distinction that caused the confusion — resolution is global, routing is per-network, so a name can resolve to an address you have no route to. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Refer to the upstream issue in plain text Matches the style used in the app's release notes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add user documentation Eleven pages plus a sidebar: a quick start that gets to a running web app, worked examples, a guide per section, and troubleshooting organised by the symptom rather than the subsystem. Written around the one constraint that explains most of the app's design — containers reach each other by address, not name — since coming from docker-compose without knowing that makes several behaviours look arbitrary. It's stated on the home page, explained under Stacks, and its limits are spelled out under Local DNS, which people will otherwise expect to fix it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>