How caddybuilds/caddy-cloudflare works
Caddy Cloudflare is a Docker image that extends Caddy with Cloudflare DNS-01 and proxy-related modules. The documented user workflow is to pull the image, provide a Caddyfile and Cloudflare API token, then let Caddy issue certificates and serve or proxy requests. Its other documented runtime capabilities include trusted client IP handling, combining trusted IP ranges, and rate limiting. The repository tree contains no runtime source excerpts, so relationships below rely on the README; implementation details beyond the Dockerfile’s existence are not inferred.
Main entry points: Dockerfile Caddy server
Components 12
Caddy image
- Caddy image
Dockerfile - Caddy server
Dockerfile - Caddyfile configuration
Certificate management
- Cloudflare API token
- DNS-01 provider
- Cloudflare DNS
Request handling
- Cloudflare IP trust
- IP range combining
- Rate limiting
Other components
- Operator
- Origin service
- Visitor
Connections 15
- Operator → Caddy image: pulls
README.md - Operator → Caddyfile configuration: configures
README.md - Operator → Cloudflare API token: provides
README.md - Caddy image → Caddy server: packages
README.md - Caddy server → DNS-01 provider: uses
README.md - Caddy server → Cloudflare IP trust: uses
README.md - Caddy server → IP range combining: uses
README.md - Caddy server → Rate limiting: uses
README.md - Caddy server → Caddyfile configuration: reads
README.md - DNS-01 provider → Cloudflare API token: uses
README.md - DNS-01 provider → Cloudflare DNS: validates via
README.md - Visitor → Caddy server: requests
README.md - Caddy server → Origin service: proxies to
README.md - Cloudflare IP trust → Caddy server: provides client IPs
README.md - Rate limiting → Caddy server: limits requests
README.md