Originally created by @deminngi on GitHub (Sep 14, 2016).
Hi Lukas,
nice script. BTW I tested it with the staging CA before going to real life.
# Path to certificate authority (default: https://acme-v01.api.letsencrypt.org/directory)
# CA="https://acme-v01.api.letsencrypt.org/directory"
CA_PROD="https://acme-v01.api.letsencrypt.org/directory"
CA_TEST="https://acme-staging.api.letsencrypt.org/directory"
CA="${CA_TEST}"
People can try the staging CA if they want to, it's documented in docs/staging.md.
I don't want to always have to configure the production CA when using this and it may (again) break a lot of setups, so this won't be changed.
@lukas2511 commented on GitHub (Sep 17, 2016):
People can try the staging CA if they want to, it's documented in [docs/staging.md](https://github.com/lukas2511/dehydrated/blob/master/docs/staging.md).
I don't want to always have to configure the production CA when using this and it may (again) break a lot of setups, so this won't be changed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @deminngi on GitHub (Sep 14, 2016).
Hi Lukas,
nice script. BTW I tested it with the staging CA before going to real life.
Path to certificate authority (default: https://acme-v01.api.letsencrypt.org/directory)
CA="https://acme-v01.api.letsencrypt.org/directory"
CA_PROD="https://acme-v01.api.letsencrypt.org/directory"
CA_TEST="https://acme-staging.api.letsencrypt.org/directory"
CA="${CA_TEST}"
@welwood08 commented on GitHub (Sep 15, 2016):
Duplicate of #72?
@lukas2511 commented on GitHub (Sep 17, 2016):
People can try the staging CA if they want to, it's documented in docs/staging.md.
I don't want to always have to configure the production CA when using this and it may (again) break a lot of setups, so this won't be changed.