#
automatic-https
Here are 3 public repositories matching this topic...
Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
-
Updated
Jul 16, 2021 - Go
Caddy Docker Custom Image
tls
cloudflare
caddy
dnspod
gandi
caddyserver
automatic-https
caddy-docker
cloudflare-dns
lego-deprecated
ntlm-transport
caddy-trace
caddyserver-custom-packages
caddy-docker-image
caddy-docker-customdns
caddy-cloudflaredns
-
Updated
Jul 25, 2021 - Dockerfile
Improve this page
Add a description, image, and links to the automatic-https topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the automatic-https topic, visit your repo's landing page and select "manage topics."
I'm managing a bunch of servers and they're running Caddy v2. The upgrade command works great for upgrading with the packages previously chosen. In the future, it's likely I'll want to add/remove packages from that list over time.
Would it make sense to add flags to add and remove packages from the caddy build on upgrade?