Support additional ACME providers #2
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, SSL certificates are provisioned using Let's Encrypt's production directory. If the only configuration provided is
SSL_DOMAIN
, that's the behaviour we want.However, it can also be useful to specify an alternate provider, so we'll expose a few extra environment variable to make that possible:
ACME_DIRECTORY
can be used to specify a different directory to use. For example, the Let's Encrypt staging environment, or another provider entirely.Some providers require EAB credentials in order to issue certificates. To support these providers, we allow providing them in
EAB_KID
andEAB_HMAC_KEY