Skip to content

Conversation

kevinmcconnell
Copy link
Collaborator

@kevinmcconnell kevinmcconnell commented Mar 5, 2024

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 and EAB_HMAC_KEY

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 prodiving them in `EAB_KID` and
`EAB_HMAC_KEY`
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.

1 participant