binhex-caddy-duckdns
binhex-caddy-duckdns
Docker app from Binhex's Repository
Overview
Requirements
Caddyfile
Place your Caddyfile at '/config/caddy/Caddyfile'.
Runtime arguments
- Web UI
http://[IP]:[PORT:8080]- Network
bridge- Shell
bash- Privileged
- false
- Extra Params
--restart=unless-stopped
Template configuration
The HTTPS port Caddy listens on. Must match https_port in your Caddyfile.
- Target
- 8443
- Default
- 8443
The HTTP port Caddy listens on (used for redirects). Must match http_port in your Caddyfile.
- Target
- 8080
- Default
- 8080
The admin edpoint port for Caddy.
- Target
- 2019
- Default
- 2019
This is the container path to your Caddy configuration file (Caddyfile) and logs.
- Target
- /config
- Default
- /mnt/user/appdata/caddy-duckdns
Duck DNS token for automatic TLS certificate issuance and renewal, sign into Duck DNS to view your token.
- Target
- DUCKDNS_TOKEN
Enable or disable healthchecks.
- Target
- ENABLE_HEALTHCHECK
- Default
- yes|no
The command or script to execute, if not specified then the script healthcheck.sh will be used (process, dns and https checking).
- Target
- HEALTHCHECK_COMMAND
The action to execute if the healthcheck command returns a non zero exit code, if not specified the action will be 'exit 1', if you want the container to exit on failure then set the action to 'kill 1'.
- Target
- HEALTHCHECK_ACTION
The hostname used when performing HTTPS and DNS healthchecking.
- Target
- HEALTHCHECK_HOSTNAME
- Default
- google.com
User ID for the running container
- Target
- PUID
- Default
- 99
Group ID for the running container
- Target
- PGID
- Default
- 100
UMASK for the running container
- Target
- UMASK
- Default
- 000
Categories
Download Statistics
Details
ghcr.io/binhex/arch-caddy-duckdnsRun binhex-caddy-duckdns on Unraid.
binhex-caddy-duckdns is listed in Community Apps for Unraid OS. Explore Unraid to build a flexible home server, NAS, or homelab.