Name |
Last commit
|
Last update |
---|---|---|
.. | ||
djangoapps | ||
envs | ||
lib | ||
static | ||
templates | ||
.coveragerc | ||
CHANGELOG.md | ||
__init__.py | ||
one_time_startup.py | ||
urls.py | ||
wsgi.py | ||
xmodule_namespace.py |
Rather than directly invoke command-line Python (and Mako) from the assets Rakefile, or call an external Python script, use a Django management command to preprocess all asset template files. An "asset template file" is defined as a static asset file with a file extension indicating that it needs to be run through a template engine prior to Sass/CoffeeScript compilation or packaging with other assets. The preprocess_assets management command will look through all of the files listed in the `STATICFILES_DIRS`, preprocessing each as needed. Preprocessing strips off the special template file extension, creating a new file in the process. Currently, the only variable accessible in an asset template file is the `THEME_NAME`, defined in the settings.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
djangoapps | Loading commit data... | |
envs | Loading commit data... | |
lib | Loading commit data... | |
static | Loading commit data... | |
templates | Loading commit data... | |
.coveragerc | Loading commit data... | |
CHANGELOG.md | Loading commit data... | |
__init__.py | Loading commit data... | |
one_time_startup.py | Loading commit data... | |
urls.py | Loading commit data... | |
wsgi.py | Loading commit data... | |
xmodule_namespace.py | Loading commit data... |