#341 Asset Pipeline in Production pro

Apr 11, 2012 | 13 minutes | Tools, Deployment, Production

The Asset Pipeline is very useful, but it can be a pain in production. Here I show why it works the way it does, and how to customize it to fit your deployment setup.

Click to Play Video ▶

Download:
source codeProject Files in Zip (107 KB)
mp4Full Size H.264 Video (39.6 MB)
m4vSmaller H.264 Video (18.2 MB)
webmFull Size VP8 Video (17.5 MB)
ogvFull Size Theora Video (46.3 MB)

Browse Source Code

Resources

          terminal
        
rails s -e production
rake assets:precompile
rake middleware
rake middleware RAILS_ENV=production
bundle
capify .
cap deploy:cold
cap deploy

          config/environments/production.rb
        
config.serve_static_assets = true # to try production on local machine

config.assets.initialize_on_precompile = false

config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect' # for nginx

          Gemfile
        
gem 'capistrano'

          Capfile
        
load 'deploy/assets'

          nginx.conf
        
location ^~ /assets/ {
  gzip_static on;
  expires max;
  add_header Cache-Control public;
}

Alternative: Precompile on Local Machine

          .gitignore
        
/public/assets

          Capfile
        
load 'deploy/assets'

          config/deploy.rb
        
namespace :deploy do
  namespace :assets do
    desc "Precompile assets on local machine and upload them to the server."
    task :precompile, roles: :web, except: {no_release: true} do
      run_locally "bundle exec rake assets:precompile"
      find_servers_for_task(current_task).each do |server|
        run_locally "rsync -vr --exclude='.DS_Store' public/assets #{user}@#{server.host}:#{shared_path}/"
      end
    end
  end
end