Enable ability to customize concurrency of gunicorn processes #184
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.
To minimize chatter in the Docker logs, it's nice to be able to disable web concurrency for gunicorn processes.
NOTE: It may be nice to have concurrency be set to
1
by default. I'm assuming the average person running this docker file will be a developer working on their eoAPI solutions locally, when high concurrency is not a strong need.