Make SASS compilation work in dev VM again #730
Merged
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
oliverroick
approved these changes
Sep 26, 2016
manoramahp
pushed a commit
to manoramahp/cadasta-platform
that referenced
this pull request
Sep 27, 2016
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.
Proposed changes in this pull request
SASS_PROCESSOR_ROOTsetting to development VM settings.STATIC_ROOTsetting we used to have in the development settings. The Django package we're using for SASS processing was looking for its output files (to check whether they were out of date) either inSASS_PROCESSOR_ROOTor, if that wasn't set, inSTATIC_ROOT. Taking out theSTATIC_ROOTsetting broke the SASS compilation.When should this PR be merged
Any time.
Risks
None.
Follow up actions
None.