Skip to content
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

Supports letsencrypt challenges #239

Merged
merged 1 commit into from
Sep 26, 2016
Merged

Conversation

arunthampi
Copy link
Contributor

So you can setup LetsEncrypt certificates natively

So you can setup LetsEncrypt certificates natively
@rauchg rauchg merged commit a506f2f into rauchg:master Sep 26, 2016
mexisme pushed a commit to devopsnz/slackin that referenced this pull request Mar 10, 2017
So you can setup LetsEncrypt certificates natively
mexisme pushed a commit to devopsnz/slackin that referenced this pull request Mar 10, 2017
So you can setup LetsEncrypt certificates natively
@devth
Copy link

devth commented Mar 22, 2017

How do we use this?

@arunthampi
Copy link
Contributor Author

@devth while setting up letsencrypt, it will provide you with a "challenge" string that your webservice should respond with when requesting the path /.well-known/acme-challenge/:id.

Once you obtain this challenge string, set the environment variable LETSENCRYPT_CHALLENGE with that string, restart your slackin service and follow along with the rest of the letsencrypt instructions.

Btw, if you're using Heroku, they support automatic SSL certs with LetsEncrypt: https://blog.heroku.com/announcing-automated-certificate-management

@devth
Copy link

devth commented Mar 22, 2017

@arunthampi thanks. I am using Heroku, and saw that announcement, but looks like it's only for paid dynos.

Would be awesome if slackin initiated the setup with LE so it was completely seamless. Still, I'm glad it supports the LE challenge. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants