``INI`` style files are used to know which files will be minified, set some
global options and also to know which files will be joined before
A good starting point to get familiar with Shrink config file format is to
read the example shrink config file. To create an example file run::
Minimize css and js files
mize all files, run::
+To mini all files, run::
$ shrink -f example_shrink.cfg all
This will use ``yuicompressor.jar`` and the ``example_shrink.cfg`` file in
current directory to compress all files.
-In case that minimzation is not desired for all files, is also possible to
-minimize individual files, or a group of files (See `Section groups`_), by
+In case that minification is not desired for all files, is also possible to
+minify individual files, or a group of files (See `Section groups`_), by
using the name(s) of each section instead of ``all`` as argument.
To list available sections, run::
Sometime can be desirable to reload modified static files without increasing
application version. In these cases the hash can be used as request parameter
instead of version number.
+It can happen your application stop working or have unespected results when
+Many times some of these problems are is easy avoid by having present the
+following notes during ``shrink.cfg`` setup:
+ * The order of the source files in each config section must be the same as
+ the one in your HTML templates.
+ * CSS files normally contains URLs which are relative to the location of
+ the file where they are declared. So for these cases the location for
+ destination file must be the same as the one for source files.
+ relative to a file location.
+ * Check that all files wich are NOT minified are being included in your