Added optional custom nginx config support #1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Give advanced users more flexibility by allowing them to include custom config files at different locations in the nginx configuration. Links in files from /share/npm (if the directory exists)
/share/npm/root.conf: Included at the very end of nginx.conf/share/npm/http.conf: Included at the end of the main http block/share/npm/server_proxy.conf: Included at the end of every proxy server block/share/npm/server_redirect.conf: Included at the end of every redirection server blockRelated Issues
NginxProxyManager/nginx-proxy-manager#178