This repository was archived by the owner on Mar 8, 2023. It is now read-only.
Update gunicorn to be compatible with new django #251
Merged
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
dwerder
added a commit
that referenced
this pull request
Mar 1, 2016
Update gunicorn to be compatible with new django
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 updates the gunicorn config to the 0.9.15 example, and changes the format of the gunicorn config file to be compatible with newer versions of django. With 1.7 (what you get with debian jessie), the "django" mode is no longer in use, and from what I can tell with my testing, the wsgi file now needs to end in .py and be in the working dir.
On debian wheezy, django is still at version 1.4.5, but has been tested to work with these new changes.