From b0dbe2f2dab908f0a12dbce121a43ea24fff609d Mon Sep 17 00:00:00 2001 From: Feanil Patel Date: Wed, 15 Apr 2015 17:27:17 -0400 Subject: [PATCH] Be more specific about where we compile sass from. There are now folders under static that have sass that should not be compiled as a part of our asset pipeline, they were getting pulled in because the wildcard for `SASS_UPDATE_DIRS` was too broad. This update makes it more specific for most folders but leaves it broad for the common folder where the xmodule has its own sass that needs compiling from a non-standard location. --- pavelib/assets.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pavelib/assets.py b/pavelib/assets.py index 054c70adcb..6887aef561 100644 --- a/pavelib/assets.py +++ b/pavelib/assets.py @@ -16,7 +16,7 @@ from .utils.cmd import cmd, django_cmd COFFEE_DIRS = ['lms', 'cms', 'common'] SASS_LOAD_PATHS = ['./common/static/sass'] -SASS_UPDATE_DIRS = ['*/static'] +SASS_UPDATE_DIRS = ['*/static/sass', 'common/static'] SASS_CACHE_PATH = '/tmp/sass-cache'