Add nginx ACME module support#47
Draft
yacchin1205 wants to merge 1 commit into
Draft
Conversation
yacchin1205
force-pushed
the
feature/nginx-acme
branch
from
951804e to
a33bdcd
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.
Summary
docker-compose.acme.ymloverride andnginx/nginx-acme.conf.templateto issue and renew TLS certificates via the nginx ACME module, as an alternative to placing certificate files under./cert. Both Let's Encrypt and UPKI ACME (with External Account Binding) are supported.Note
nginx-acme.conf.templatereplaces the wholenginx.confinstead of being aconf.dfragment becauseload_moduleis main-context only; HTTPS proxy behavior matchesnginx.conf.template, only ACME-specific directives are added.