I’m reading now about assets in Rails. Because I got errors on Heroku
that my assets are not pre-compiled. On local machine everything works
fine, on Heroku they suddenly are not pre-complied.
The guide says:
Starting with version 3.1, Rails defaults to concatenating all JavaScript
files into one master .js file and all CSS files into one master .css
file.
In production, Rails inserts an MD5 fingerprint into each filename so that
the file is cached by the web browser.
This is part of Rails’ “fast by default” strategy as outlined by DHH
in his keynote at RailsConf 2011.
What? Rails is using their own technologies exactly as they were
designed to be used. I don’t know what you mean by the comment in your
subject line.
I’m reading now about assets in Rails. Because I got errors on Heroku
that my assets are not pre-compiled. On local machine everything works
fine, on Heroku they suddenly are not pre-complied.
It’s a good thing that you’re finally reading the guides since it’s
obvious you are not understanding the asset pipeline.
The guide says:
Starting with version 3.1, Rails defaults to concatenating all JavaScript
files into one master .js file and all CSS files into one master .css
file.
In production, Rails inserts an MD5 fingerprint into each filename so that
the file is cached by the web browser.
This is part of Rails’ “fast by default” strategy as outlined by DHH
in his keynote at RailsConf 2011.