From fb674f18cb4e27099035e20c77e67b40346f143c Mon Sep 17 00:00:00 2001 From: Jay Date: Wed, 10 Jun 2026 22:29:22 +0200 Subject: [PATCH] docs: Clarify dokploy-network is auto-attached by Dokploy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Document that services not exposed via Cloudflare Tunnel should not declare any network in their compose file — Dokploy attaches its own dokploy-network automatically on deploy. Note traccar's explicit declaration is redundant legacy. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 9a0d0c8..0f5418f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -30,8 +30,12 @@ exactly. **Network model:** A single Cloudflare Tunnel (`cloudflared/`) creates and owns the `cloudflare-exposed` external bridge network. Services that need internet -exposure connect to this network. Exception: `traccar` -uses `dokploy-network`. +exposure declare and connect to this network. Services +that don't need Cloudflare exposure should **not** declare +any network in their compose file — Dokploy attaches its +own `dokploy-network` automatically on deploy (e.g. `n8n`, +`plex`, `watchtower`). `traccar` predates this and still +declares `dokploy-network` explicitly, which is redundant. **Container management:** Watchtower handles automatic image updates using label-based opt-in