NGF: Update examples in NginxProxy patch documentation #954
Conversation
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
github-actions
bot
added
documentation
ciarams87
force-pushed
the
feat/ngf-proxy-patch
branch
from
855b0bf to
7cf9013
Compare
sjberman
approved these changes
Aug 13, 2025
ADubhlaoich
approved these changes
Aug 14, 2025
sjberman
pushed a commit
that referenced
this pull request
Aug 14, 2025
feat: update examples in NginxProxy patches
bjee19
pushed a commit
that referenced
this pull request
Aug 14, 2025
feat: update examples in NginxProxy patches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
Update the documentation on how to use the NginxProxy patch functionality to use more descriptive and informative examples.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩