Conversation
If we need to provide any custom files such as custom error handlers or ANY other type of customization, we can put it in the `custom` directory which maps to `/var/www/custom` in the container.
akamal4
approved these changes
Nov 17, 2025
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
2 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.
This improvement adds a mapping from
customto/var/www/customwithin the Nginx Proxy Manager container. This can then be used to store any type of custom configuration or content that NPM needs, but in a way that can be consistent across our servers. If it isn't needed, it can be ignored. If it is needed, a proxy host's custom Nginx configuration can reference any files placed here.