Name |
Last commit
|
Last update |
---|---|---|
.. | ||
assets.rake | ||
deploy.rake | ||
django.rake | ||
docs.rake | ||
helpers.rb | ||
i18n.rake | ||
jasmine.rake | ||
prereqs.rake | ||
quality.rake | ||
tests.rake | ||
workspace.rake |
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 |
---|---|---|
.. | ||
assets.rake | Loading commit data... | |
deploy.rake | Loading commit data... | |
django.rake | Loading commit data... | |
docs.rake | Loading commit data... | |
helpers.rb | Loading commit data... | |
i18n.rake | Loading commit data... | |
jasmine.rake | Loading commit data... | |
prereqs.rake | Loading commit data... | |
quality.rake | Loading commit data... | |
tests.rake | Loading commit data... | |
workspace.rake | Loading commit data... |