Generate Nginx configs from entrypoint and tests #50
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.
Generate Nginx configs from entrypoint instead of modifying live pre-existing files.
This is a more "purely functional" approach that improves stability, debuggability, etc.
It will also allow having a completely custom
nginx.conffile to be used instead of the generated one.It's a major refactor, but the tests ensure everything is working.
This (and the equivalent in
uwsgi-nginx-flask) will solve: #49It's also the first step to allow having a completely custom
nginx.conf, that will solve:#36
tiangolo/uwsgi-nginx-flask-docker#116
tiangolo/uwsgi-nginx-flask-docker#108
tiangolo/uwsgi-nginx-flask-docker#103