This role installs and configures the caddy web server. The user can specify any http configuration parameters they wish to apply their site. Any number of sites can be added with configurations of your choice.
None
See Caddyfile docs. Notice the | used to include a multi-line string.
default:
caddy_config: |
http://localhost:2020
respond "Hello, world!"If you wish to use a template for the config you can do this:
caddy_config: "{{ lookup('template', 'templates/Caddyfile.j2') }}"default:
caddy_os: linuxdefault:
caddy_update: trueChanging this variable will reinstall Caddy with the new packages if caddy_update is enabled. Check https://caddyserver.com/download for available packages.
default:
caddy_packages: []This allows Caddy to open a low port (under 1024 - e.g. 80, 443).
default:
caddy_setcap: truedefault:
caddy_systemd_capabilities_enabled: false
caddy_systemd_capabilities: "CAP_NET_BIND_SERVICE"NOTE: This feature requires systemd v229 or newer and might be needed in addition to caddy_setcap: yes.
Supported:
- Debian 9 (stretch)
- Fedora 25
- Ubuntu 16.04 (xenial)
RHEL/CentOS has no release that supports systemd capability controls at this time.
Add environment variables to the systemd script.
default:
caddy_environment_variables: {}Example usage:
caddy_environment_variables:
FOO: bar
SECONDVAR: spamdefault:
caddy_additional_args: ""Example for LetsEncrypt staging:
caddy_additional_args: "-ca https://acme-staging.api.letsencrypt.org/directory"This role uses the GitHub releases list to check when a new version is available. GitHub has some fairly agressive rate-limiting which can cause failures. You can set your GitHub token to increase the limits for yourself when running the role (e.g. if deploying many servers behind a NAT or running this role repeatedly as part of a CI process).
default:
caddy_github_token: ""---
- hosts: all
become: yes
roles:
- role: caddy_ansible.caddy_ansible
caddy_config: |
files.example.com
encode gzip
file_server browse {
root /home/caddy/
}Example with DigitalOcean DNS for TLS:
---
- hosts: all
roles:
- role: caddy_ansible.caddy_ansible
caddy_environment_variables:
DO_AUTH_TOKEN: "your-token-here"
caddy_systemd_capabilities_enabled: true
caddy_systemd_network_dependency: false
caddy_packages: ["github.com/caddy-dns/lego-deprecated"]
caddy_config: |
nextcloud.example.com {
log
reverse_proxy http://localhost:8080 {
header_up Host {http.request.host}
header_up X-Real-IP {http.request.remote.host}
header_up X-Forwarded-For {http.request.remote.host}
header_up X-Forwarded-Port {http.request.port}
header_up X-Forwarded-Proto {http.request.scheme}
}
tls [email protected] {
dns lego_deprecated digitalocean
}
}If the service fails to start you can figure out why by looking at the output of Caddy.
systemctl status caddy -lIf something doesn't seem right, open an issue!
Pull requests are welcome. Please test your changes beforehand with vagrant:
vagrant up
vagrant provision # (since it already provisioned there should be no changes here)
vagrant destroy
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent