Your assets are covered.
With Rails' default asset caching, CSS and JS are concatenated (not even minified) at runtime when that bundle is first requested. Not good enough. AssetHat can automatically:
Easily minify and bundle CSS and JS on deploy to reduce file sizes and HTTP requests.
Load popular <strong>third-party JS</strong> (like jQuery and Prototype) from Google’s CDN when in production, or from localhost in development.
Force image URLs in your CSS to use <strong>CDN subdomains</strong>, not just the current host.
Add an image's last Git commit ID to its CSS URLs to <strong>bust browser caches</strong> (e.g., /images/foo.png?ab12cd34e).
After setup, you can use these in your layouts and views:
And this in your deploy script:
Tested with Rails 2.3.x.
Install the gem:
gem install asset_hat
Configure the gem:
If you're using Bundler 0.9+:
Add to your app's Gemfile: gem 'asset_hat', '0.x.x'
Command-line: bundle install
If you're using Rails' config.gem, add to your app's config/environment.rb:
config.gem 'asset_hat', :version => '0.x.x'
Add to your app's Rakefile:
Create the default config file:
In your app, open the new file at config/assets.yml, and set up your CSS/JS bundles according to that file's example.
Minify your bundles:
This minifies all of the CSS/JS files listed in config/assets.yml, concatenates the minified code into bundle files, and adds CDN asset hosts and cache-busting commit IDs to image URLs in your CSS.
Set your deployment script to run rake asset_hat:minify after deploying your latest CSS/JS. This overwrites previously minified bundles, and leaves your original CSS/JS files intact.
If you manage deployments with Capistrano, see the gem's packaged example at lib/asset_hat/capistrano.rb.
Additional settings are supported in config/assets.yml:
engine: Indicates how CSS and JS are minified; omit this setting to use the defaults. By default, CSS is minified with rgrove/cssmin (a Ruby port of Lecomte's YUI Compressor and Schlueter's PHP cssmin), and JS is minified with rgrove/jsmin (a Ruby port of Crockford's JSMin).
If the default engines cause problems by minifying too strongly, try switching each to weak. The weak engines are much safer, but don't save as many bytes.
vendors: Currently only allows for setting the jQuery version number:
js: vendors: jquery: version: 1.4
In the future, this will be used for configuring the retrieval of other third-party code.
In your layouts and views, instead of these:
<%= include_css :bundle => 'application' %> <%= include_js :bundle => 'application' %>
These turn into:
Have an enormous app? You can integrate gradually, using AssetHat alongside Rails' default asset caching.
If your environment has config.action_controller.perform_caching set to true (e.g., in production), the layout/view will include minified bundle files. Otherwise, the separate, unminified files will be included, based on the bundle contents you define in config/assets.yml.
You can also include single files as expected:
<%= include_css 'reset', 'application' %> <%= include_js 'plugin.min', 'application' %>
Or include multiple bundles at once:
<%= include_js :bundles => %w[plugins common] %>
When including multiple bundles at once, this yields one <link> or <script> element per bundle.
You may want to use multiple bundles to separate plugins (rarely changed) from application code (frequently changed). If all code is in one huge bundle, then whenever there's a change, browsers have to re-download the whole bundle. By using multiple bundles based on change frequency, browsers cache the rarely changed code, and only re-download the frequently changed code.