⚡ Allow passing overrides to frontend nginx config #3602
Closed
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 allows Docker users to mount an arbitrary number of additional nginx config files at
/etc/nginx/overrides.d
which will then be included in the configuration used. Passed config files take precedence over both the directives in thehttp
block. The followingserver
block could also be overwritten as the first match takes precedence.Example in a compose setup:
where
logging.conf
looks likeUsers that don't use this feature will not be affected and do not need to change anything.
I would like to disable access logging for the
frontend
container as it is behind another reverse proxy anyways and logs can get quite noisy/heavy.access_log /dev/stdout
is hard coded in the nginx config, so there is no way of configuring this currently.I am not entirely sure if documentation lives in this repo as well and needs to be updated. In case yes, please lmk and I can do this still.