Repository navigation
Conversation
kemko
force-pushed
the
support_acme_directory_change
branch
from
September 10, 2024 19:42
ea4f4ee to
fefc6b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For now, reproxy only allows the use of the default ACME directory, which is https://acme-v02.api.letsencrypt.org/directory.
With these changes, users can change the directory to any other. It can be LE staging environment (see https://letsencrypt.org/docs/staging-environment/) or even other compatible ACME provider, e.g. zerossl.