search

ndbroadbent / turbo-sprockets-rails3

Speeds up your Rails 3 assets:precompile by only recompiling changed files, and only compiling once to generate all assets
MIT License
975 stars 78 forks source link

Asset rollback? #54

Open ellisera opened 11 years ago

ellisera commented 11 years ago

Hi, new to Capistrano and turbo-sprockets-rails3, so my apologies if I'm going over covered ground. I have tried to search for this online before I posted here.

  1. Does turbo-sprockets-rails3 have any way to rollback assets?
  2. Is there a good way to integrate this with Capistrano's deploy:rollback?

I've tried setting a backup task for the manifest files (and also at another point for the asset folder). It's supposed to take place before assets:precompile, and there's another task that is supposed to copy back the file (or folder depending on which version of my code we're talking about) during rollback, before the thin servers restart. Unfortunately I've seemed to hit a bit of a dead end with this method.

zmillman commented 11 years ago

I just encountered this issue as well

ScotterC commented 11 years ago

It's not clear to me how this is supposed to work. From this pull request it looks like all that is needed is the assets_manifest.yml in every release path. With turbo sprockets this supposed to work quickly. I've now edited my precompile:assets task on deploy to copy that file over but the rollbacks seem to recompile everything.