Fix venv being created in Dockerfile#69
Merged
Merged
Conversation
There will be more config files to come so it's cleaner to have them together than littering the root directory with more files.
This will make it easy to maintain a consistent config without relying on invocation via pipenv.
`pipenv run` creates a venv because it cannot detect that a --system install was done. The solution is to invoke gunicorn directly.
MarkKoz
added
type: bug
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.
Fixes #66
pipenv runcreates a venv because it cannot detect that a --system install was done. The solution is to invoke gunicorn directly. To avoid specifying config options in both the Dockerfile and the Pipfile, a config file for gunicorn was created.