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 |
---|---|---|
.. | ||
cms | Loading commit data... | |
devgroups | Loading commit data... | |
README.txt | Loading commit data... | |
__init__.py | Loading commit data... | |
acceptance.py | Loading commit data... | |
aws.py | Loading commit data... | |
common.py | Loading commit data... | |
content.py | Loading commit data... | |
dev.py | Loading commit data... | |
dev_edx4edx.py | Loading commit data... | |
dev_ike.py | Loading commit data... | |
dev_int.py | Loading commit data... | |
dev_mongo.py | Loading commit data... | |
dev_with_worker.py | Loading commit data... | |
devplus.py | Loading commit data... | |
discussionsettings.py | Loading commit data... | |
edx4edx_aws.py | Loading commit data... | |
jasmine.py | Loading commit data... | |
static.py | Loading commit data... | |
test.py | Loading commit data... |