Made documentation of config.assets.precompile slightly more explicit.
Having read the previous version of the documentation, I was surprised
when a wildcarded CSS pattern in precompile picked up a whole load of
SCSS files! I've amended lines 426 onwards to document the behaviour.
@@ -423,12 +423,14 @@ It is important that this folder is shared between deployments so that remotely
NOTE. If you are precompiling your assets locally, you can use +bundle install --without assets+ on the server to avoid installing the assets gems (the gems in the assets group in the Gemfile).
-The default matcher for compiling files includes +application.js+, +application.css+ and all non-JS/CSS files (i.e., +.coffee+ and +.scss+ files are *not* automatically included as they compile to JS/CSS):
+The default matcher for compiling files includes +application.js+, +application.css+ and all non-JS/CSS files (this will include all image assets automatically):
+NB: the matcher (and other members of the precompile array; see below) is applied to the final compiled file name. This means that anything that compiles to JS/CSS is excluded, as well as raw JS/CSS files; for example, +.coffee+ and +.scss+ files are *not* automatically included as they compile to JS/CSS.