caddy-reverse-proxy

To configure a Caddy reverse proxy with automatic HTTPS, you write a Caddyfile defining your domain and backend service, and Caddy automatically handles Let's Encrypt certificate acquisition. This streamlines secure service exposure for homelab setups.

Routing multiple subdomains to Docker services using Caddy involves defining multiple site blocks in your Caddyfile and configuring your Docker network. Caddy supports path-based routing and domain rules to direct traffic to specific backend containers.

Yes, you can use Caddy to set up basic auth and IP restrictions for internal web services. Caddyfile syntax supports security features including basic authentication and IP whitelisting to protect exposed homelab applications.

Caddy supports websocket proxying and dynamic configuration reloads out of the box. The Caddyfile allows you to configure reverse proxy rules that maintain websocket connections, and you can reload configurations dynamically without downtime.

To deploy Caddy in Docker with environment variables, use a docker-compose configuration that defines the Caddy service and its network. Caddy integrates environment variables into the Caddyfile, allowing flexible dynamic configuration across different deployment contexts.