LetsEncrypt-DNS 2.0.1

• Correct autocmd/autorestart behavior with wildcard certificates
• Correct wrongly revokation of wilcard certificates after their creation

LetsEncrypt-DNS 2.0.0

• Switch to ACME v2 servers, which allow wildcard certificates generation (eg. *.example.com)
• Update Certbot to 0.22.2 to supports the ACME v2 servers
• Update Lexicon to 0.22.1 adding support for following DNS providers: AuroraDNS, Gehirn Infrastructure Service, OnApp and Sakura Cloud
• Allow use of old ACME v1 servers through LEXICON_ACME_V1 environment variable
• Correct deploy hook about files/directory permission fixation

LetsEncrypt-DNS 1.5.0

• Update Lexicon to 2.1.16 (add DNS Linode provider)
• Update Certbot to 0.20.0

LetsEncrypt-DNS 1.4.3

• Update Lexicon to v2.1.14, with support of Zonomi DNS provider.

LetsEncrypt-DNS 1.4.2

• Correct python babel dependency of lexicon which is actually required to run the software.

Warning:
Version LetsEncrypt-DNS 1.4.1 is broken. If you pulled version 1.4.1, you must at least upgrade to 1.4.2 in order to allow you certificates to be renewed.

LetsEncrypt-DNS 1.4.1

• Upgrade Lexicon to v2.1.11, providing support for ClouDNS API.

LetsEncrypt-DNS 1.4.0

• New environment variables CERTS_DIRS_MODE, CERTS_FILES_MODE, CERTS_USER_OWNER and CERTS_GROUP_OWNER to configure certificates files/folders permissions, owner and group.
• New domains.conf option autocmd-containers to call reload commands on target containers during certificate renew.
• Fix certificates revokation and deletion.
• Update documentation.

LetsEncrypt-DNS 1.3.1

• Auto-export of PFX certificates when Let's Encrypt PEM certificates are created, renewed or upon container creation/recreation (activated by EXPORT_PFX environment variable)
• Update documentation
• Update Alpine packages
• Update CertBot to 0.19.0

LetsEncrypt-DNS 1.3.0

• Update Certbox to 0.18.2
• Correct README.md to advert about GoDaddy support in Lexicon

LetsEncrypt-DNS 1.2.0

• Update Certbot to 0.17.0
• Refactor domains.conf watching and automated containers reload upon certificate update.
  Previous approach was to use inotify, but inotify may not work with containers in virtualized enviroments. New approach is to check periodically hashes of relevant files, and trigger update when they changes: this approach will work for all environments.