Asset compilers and processors¶
The asset building process consists of multiple steps. At it’s simplest, only the directives are processed and dependencies are included into the build files. The build process can do much more though, like compiling less files with lessjs or compressing js files with uglifyjs.
Each build follows these fives steps that can be customized for your environment.
- Save to filesystem
The first step is where dependencies are managed. Gears looks for directives within assets and includes them within the asset file. As explained elsewhere, directives are simple comments in the header of script or css files. For example:
/* *= require jquery *= require underscore *= require backbone */
It’s not common to change the preprocess step, but if you wish to do so, this can be done by modifying the GEARS_PREPROCESSORS setting.
Various compilers are just a pip install away. You can browse plugins that are available at the Gears repositories github page. If you find a compiler not supported, it’s easy to create a plugin of your own.
The third step is where files are postprocessed. By default, Django Gears runs the gears.processors.HexdigestPathsProcessor for css files. This processor replaces url declarations in the css with fingerprinted versions. Note, this processor only works if all paths in url declarations refer to local files.
The post processors can be modified with the GEARS_POSTPROCESSORS setting.
The fourth step is where tools like SlimIt, UglifyJS, or clean-css are run. These produce minified files and minimize bandwidth requirements.
For users of Python 2.X, Gears has built-in support for SlimIt and cssmin.
Other compilers are just a pip install away. You can browse plugins that are available at the Gears repositories github page.
5. Save to filesystem¶
The fifth step is where processed files are saved to the file system. The destination directory is controlled by the GEARS_ROOT setting.
Unless GEARS_FINGERPRINTING is set to false, the asset will be fingerprinted and added to the .manifest.json file.
During this step, the file can optionally be gzipped. This is controlled by the GEARS_GZIP setting.