Fabio/docker-letsencrypt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
📜 Automatic SSL Certificate Generation for Duck DNS Domains
28 commits 2 branches 0 tags 79 KiB
Shell 89.9%
Dockerfile 10.1%
Find a file
Maksim 9f593f37a5 Merge branch 'master' of github.com:maksimstojkovic/docker-letsencrypt
2019-12-27 03:44:27 +11:00
.github/workflows changed username 2019-12-26 03:07:44 +11:00
scripts email now optional, and wildcard defaults to false 2019-12-10 23:38:25 +11:00
Dockerfile changed username 2019-12-27 03:44:13 +11:00
LICENSE add license 2019-12-07 19:20:17 +11:00
README.md changed username 2019-12-26 03:18:41 +11:00

README.md

Let's Encrypt for Duck DNS

Build Status Docker Pulls Docker Stars Image Size Image Version Image Commit

Automatically generates Let's Encrypt certificates using a lightweight Docker container without requiring any ports to be exposed for DNS challenges.

Variables

  • DUCKDNS_TOKEN: Duck DNS account token (obtained from Duck DNS)
  • DUCKDNS_DOMAIN: Full Duck DNS domain (e.g. test.duckdns.org)
  • LETSENCRYPT_EMAIL: Email used for certificate renewal notifications (optional)
  • LETSENCRYPT_WILDCARD: true or false, indicating whether the SSL certificate should be for subdomains only of DUCKDNS_DOMAIN (i.e. *.test.duckdns.org), or for the main domain only (i.e. test.duckdns.org) (default: false)
  • TESTING: true or false, indicating whether a staging SSL certificate should be generated or not (default: false)

Note: The format of DUCKDNS_DOMAIN should be the same regardless of the value of LETSENCRYPT_WILDCARD.

Volumes

  • <certs>:/etc/letsencrypt: A named or hosted volume which allows SSL certificates to persist and be accessed by other containers

Note: If a hosted volume is used, the volume should be mounted in an unused directory in another container to prevent access conflicts.