Skip asset pre-compilation when deploying if the assets didn't change

deploy.rb

namespace :deploy do
  namespace :assets do
    task :precompile, :roles => :web, :except => { :no_release => true } do
      from = source.next_revision(current_revision)
      if capture("cd #{latest_release} && #{source.local.log(from)} vendor/assets/ app/assets/ | wc -l").to_i > 0
        run %Q{cd #{latest_release} && #{rake} RAILS_ENV=#{rails_env} #{asset_env} assets:precompile}
      else
        logger.info "Skipping asset pre-compilation because there were no asset changes"
      end
    end
  end
end

Great, never had time to find out by myself how to do that. BTW: I had to remove vendor/assets path from line 5 because it doesn't exist in my repo, and git returns an error if path does not exist in repo.

Great, never had time to find out by myself how to do that. BTW: I had to remove vendor/assets path from line 5 because it doesn't exist in my repo, and git returns an error if path does not exist in repo.

Thanks,

Thanks,

You also probably should check for Gemfile.lock, as some assets are provided by gems.

You also probably should check for Gemfile.lock, as some assets are provided by gems.

This will fail on the first deploy because current_revision is not yet defined and the command capistrano uses to find current_revision will fail. You can add :on_error => :continue to the task definition and it won't fail, but it will skip it and you'll have to deploy twice on the first go in order to build you assets, which is still kind of hacky.

This will fail on the first deploy because current_revision is not yet defined and the command capistrano uses to find current_revision will fail. You can add :on_error => :continue to the task definition and it won't fail, but it will skip it and you'll have to deploy twice on the first go in order to build you assets, which is still kind of hacky.

Simple workaround for first deploy:
https://gist.github.com/4079213

Simple workaround for first deploy:
https://gist.github.com/4079213

Hi all, is it essential to add lib/*/app/assets to my own list of locations to git log? Currently I have some gems downloaded, located under the /lib directory, and I sometimes need to edit their assets.

Hi all, is it essential to add lib/*/app/assets to my own list of locations to git log? Currently I have some gems downloaded, located under the /lib directory, and I sometimes need to edit their assets.