Synchronises Assets between Rails and S3
Pull request Compare This branch is 2 commits ahead, 488 commits behind AssetSync:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Asset Sync

Synchronises Assets between Rails and S3.

Asset Sync is built to run with the new Rails Asset Pipeline feature of Rails 3.1. After you run bundle exec rake assets:precompile:primary RAILS_ENV=production RAILS_GROUPS=assets (optionally set RAILS_GROUPS if you're using assets group in you Gemfile) only your digest assets will be synchronised to your S3 bucket, optionally deleting unused files and only uploading the files it needs to.

This was initially built and is intended to work on Engine Yard


Add the gem to your Gemfile

gem "asset_sync"

The following steps are now optional as of version 0.1.7 there is a built-in initializer lib/engine.rb

Generate the rake task and config files

rails g asset_sync:install

If you would like to use a YAML file for configuration instead of the default (Rails Initializer) then

rails g asset_sync:install --use-yml


Configure config/environments/production.rb to use Amazon S3 as the asset host and ensure precompiling is enabled.

# config/environments/production.rb
config.action_controller.asset_host = do |source, request|
  request.ssl? ? "https://#{ENV['AWS_BUCKET']}" : "http://#{ENV['AWS_BUCKET']}"

We support two methods of configuration.

  • Rails Initializer
  • A YAML config file

Using an Initializer is the default method and is best used with environment variables. It's the recommended approach for deployments on Heroku or Engine Yard.

Using a YAML config file is a traditional strategy for Capistrano deployments. If you are using Moonshine (which we would recommend) then it is best used with shared configuration files.

The recommend way to configure asset_sync is by using environment variables however it's up to you, it will work fine if you hard code them too. The main reason is that then your access keys are not checked into version control.

Initializer (config/initializers/asset_sync.rb)

The generator will create a Rails initializer at config/initializers/asset_sync.rb.

AssetSync.configure do |config|
  config.aws_access_key = ENV['AWS_ACCESS_KEY']
  config.aws_access_secret = ENV['AWS_ACCESS_SECRET']
  config.aws_bucket = ENV['AWS_BUCKET']
  # config.aws_region = 'eu-west-1'
  config.existing_remote_files = "keep"

YAML (config/asset_sync.yml)

If you used the --use-yml flag, the generator will create a YAML file at config/initializers/asset_sync.rb.

defaults: &defaults
  aws_access_key: "<%= ENV['AWS_ACCESS_KEY'] %>"
  aws_access_secret: "<%= ENV['AWS_ACCESS_SECRET'] %>"
  # You may need to specify what region your S3 bucket is in
  # aws_region: "eu-west-1"

  <<: *defaults
  aws_bucket: "rails-app-development"
  existing_remote_files: keep # Existing pre-compiled assets on S3 will be kept

  <<: *defaults
  aws_bucket: "rails-app-test"
  existing_remote_files: keep

  <<: *defaults
  aws_bucket: "rails-app-production"
  existing_remote_files: delete # Existing pre-compiled assets on S3 will be deleted

Environment Variables

Add your Amazon S3 configuration details to heroku

heroku config:add AWS_ACCESS_KEY=xxxx
heroku config:add AWS_ACCESS_SECRET=xxxx
heroku config:add AWS_BUCKET=xxxx

Or add to a traditional unix system

export AWS_ACCESS_KEY=xxxx
export AWS_BUCKET=xxxx

Available Configuration Options

  • aws_access_key: your Amazon S3 access key
  • aws_access_secret: your Amazon S3 access secret
  • aws_region: the region your S3 bucket is in e.g. eu-west-1
  • existing_remote_files: what to do with previously precompiled files, options are keep or delete

Amazon S3 Multiple Region Support

If you are using anything other than the US buckets with S3 then you'll want to set the region. For example with an EU bucket you could set the following with YAML.

  # ...
  aws\_region: 'eu-west-1'

Or via the initializer

AssetSync.configure do |config|
  # ...
  config.aws_region = 'eu-west-1'


  1. Add some before and after filters for deleting and uploading
  2. Support more cloud storage providers
  3. Better test coverage


Have borrowed ideas from:


MIT License. Copyright 2011 Rumble Labs Ltd.