New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Letsencypt http challenge #538
Letsencypt http challenge #538
Conversation
created empty acme.json to hold letsencrypt certificates
create a volume for the letsencrypt certificate
environment variable for email to provide to let's encrypt
This reverts commit 31bbbfa.
added new compose file forDocker-compose with let's encrypt : HTTP Challenge
added instructions for usage of Docker-compose with let's encrypt
added chmod 600 for ssl/acme.json in README.md
Run: | ||
|
||
``` | ||
cp .en.template .env |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A minor note while I just read this:
cp .en.template .env | |
cp .env.template .env |
Regards, Enrico
Hey @benlooning, Thanks a lot for this PR. Actually, the docker-compose.yml file from the root directory is really targetted at development only and should not be used for production environments at all. Therefore, adding Let's Encrypt in this environment is a bit useless. But we are building special docker images that can be used along Let's encrypt. I recently merged #698 that is adding a brand new docker-compose file for production setups (with Let's Encrypt support). This docker-compose file is using the "official" Docker images and not the development ones (so the JS is minified, etc...) I'm closing this PR as it is superseded with #698 |
As so many users seem to have issues with the self-signed certificates I thought it would be a good idea to create a dedicated compose file for using traefik letsencypt http challenge. Maybe there is a better way, but this was the best I could think of.