Skip to content

docs: Clarify dokploy-network is auto-attached by Dokploy #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
finallyjay merged 1 commit into from
Jun 10, 2026
Merged

docs: Clarify dokploy-network is auto-attached by Dokploy #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading