Feature/staticfiles #472
Open
Feature/staticfiles #472
Conversation
This file contains 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
…a directory 'staticfiles' in the project root
…manually using STATIC_URL
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.
This branch updates the project to explicitly define the STATIC_ROOT, which is project root level directory called 'staticfiles'. It also updates the templates to make use of the 'static' template tag instead of manually prepending {{STATIC_URL}} to static assets.
These changes apply some best practices and should also simplify the wiki's nginx conf. The multiple /static/ blocks should no longer be needed. 'collectstatic' should now bring all those relevant assets to the 'staticfiles' directory. So, you can now just have a single /static/ block in the nginx config.