|
|
1 年間 前 | |
|---|---|---|
| .. | ||
| README.md | 1 年間 前 | |
| docker-entrypoint.sh | 1 年間 前 | |
| update-cert.template.txt | 1 年間 前 | |
Docker-compose certbot configurations with Backward compatibility (without certbot container).
Use docker-compose --profile certbot up to use this features.
Get letsencrypt certs
set .env values
NGINX_SSL_CERT_FILENAME=fullchain.pem
NGINX_SSL_CERT_KEY_FILENAME=privkey.pem
NGINX_ENABLE_CERTBOT_CHALLENGE=true
CERTBOT_DOMAIN=your_domain.com
CERTBOT_EMAIL=example@your_domain.com
excecute command:
sudo docker network prune
sudo docker-compose --profile certbot up --force-recreate -d
then after the containers launched:
sudo docker-compose exec -it certbot /bin/sh /update-cert.sh
Edit .env file and sudo docker-compose --profile certbot up again.
set .env value additionally
NGINX_HTTPS_ENABLED=true
excecute command:
sudo docker-compose --profile certbot up -d --no-deps --force-recreate nginx
Then you can access your serve with HTTPS.
https://your_domain.com
For SSL certificates renewal, execute commands below:
sudo docker-compose exec -it certbot /bin/sh /update-cert.sh
sudo docker-compose exec nginx nginx -s reload
CERTBOT_OPTIONS key might be helpful for testing. i.e.,
CERTBOT_OPTIONS=--dry-run
To apply changes to CERTBOT_OPTIONS, regenerate the certbot container before updating the certificates.
sudo docker-compose --profile certbot up -d --no-deps --force-recreate certbot
sudo docker-compose exec -it certbot /bin/sh /update-cert.sh
Then, reload the nginx container if necessary.
sudo docker-compose exec nginx nginx -s reload
To use cert files dir nginx/ssl as before, simply launch containers WITHOUT --profile certbot option.
sudo docker-compose up -d