Skip to content

[Cloudflared] feat: Attach to dokploy-network #35

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 14, 2026
Merged

[Cloudflared] feat: Attach to dokploy-network #35

Show file tree
Hide file tree
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
5 changes: 5 additions & 0 deletions cloudflared/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,11 @@ This service creates the shared `cloudflare-exposed` bridge
network. Any service that needs external access must join
this network.

The tunnel also attaches to the `dokploy-network` so it can
reach services that are only published on that network
(those that don't declare `cloudflare-exposed`). Dokploy
provides `dokploy-network` automatically on deploy.

## How It Works

1. The `cloudflared` container establishes a tunnel
Expand Down
1 change: 1 addition & 0 deletions cloudflared/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ services:
start_period: 30s
networks:
- cloudflare-exposed
- dokploy-network
environment:
- TUNNEL_TOKEN=${CLOUDFLARE_TUNNEL_TOKEN}
logging:
Expand Down