Releases: pini-gh/acme-companion
Releases · pini-gh/acme-companion
v2.0.2-dns2
Enable standalone certificate configuration for a container when LETSENCRYPT_HOST is set but not VIRTUAL_HOST.
No need for the /app/letsencrypt_user_data
file in this case.
v2.0.2-dns1
Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v2.0.2
Support DNS mode challenge and wildcard domain certificates.
Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v2.0.1
Support DNS mode challenge and wildcard domain certificates.
Let nginx-proxy handle default certificate generation
The default certificate is needed by nginx-proxy before the letsencrypt companion can generate it.
This version requires pinidh/nginx-proxy.
Updated to nginx-proxy/docker-letsencrypt-nginx-proxy-companion v1.13
- Rebase against nginx-proxy/docker-letsencrypt-nginx-proxy-companion v1.13
- Force certificate renewal when the corresponding .companion flag file doesn't exist in the nging-proxy certs volume.
First acme.sh based release
Uses acme.sh as Let's Encrypt client (instead of simp_le) and brings support for:
- DNS mode challenge
- Wildcard domain certificates