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

README: Add warning/advice about HTTPS API. #169

Merged
merged 2 commits into from
Jun 12, 2019

Conversation

cpu
Copy link
Contributor

@cpu cpu commented May 30, 2019

This PR updates the README to add a brief description of the tls configuration options. In particular using tls = "letsencrypt" is recommended and a warning is added about using tls = "cert" and allowing the certificate to expire.

For more background see:

This commit updates the README to add a brief description of the `tls`
configuration options. In particular using `tls = "letsencrypt"` is
recommended and a warning is added about using `tls = "cert"` and
allowing the certificate to expire.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.831% when pulling b271f5e on cpu:cpu-readme-https-warning into af5d256 on joohoi:master.

@cpu
Copy link
Contributor Author

cpu commented Jun 7, 2019

@joohoi Gentle ping on this PR. I think it will be a quick review (no code, just words).

@joohoi
Copy link
Owner

joohoi commented Jun 12, 2019

Thanks for the PR, sorry it took a while to get around it.

@joohoi joohoi merged commit e1f1d6a into joohoi:master Jun 12, 2019
@cpu
Copy link
Contributor Author

cpu commented Jun 12, 2019

Thanks @joohoi !

@cpu cpu deleted the cpu-readme-https-warning branch June 12, 2019 12:47
jacobmyers-codeninja pushed a commit to jacobmyers-codeninja/acme-dns that referenced this pull request Sep 30, 2020
This commit updates the README to add a brief description of the `tls`
configuration options. In particular using `tls = "letsencrypt"` is
recommended and a warning is added about using `tls = "cert"` and
allowing the certificate to expire.
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.

None yet

4 participants