I'm using Rails 3.1rc5, and have been using my own :precompile_assets task in capistrano, which runs assets:precompile. I run it by : after "deploy:symlink", "deploy:precompile_assets"
With capistrano 2.8.0, can I remove my current task ? Is assets:precompile now performed by capistrano using the deploy:assets:precompile task I've seen mentioned (e.g. https://github.com/capistrano/capistrano/issues/81) ? Do I need to call deploy:assets:precompile myself ? Why are there no deploy:assets:* tasks when I run cap -vT ? Secondly, I currently use "group :assets" in capistrano as I've seen it recommended as a way to exclude asset related gems from production application processes, as they aren't needed if precompile is used. Does capistrano include these :asset gems for running assets:precompile, then exclude then for running the actual production process ? Currently I see the asset gems in my application processes if I check Gem.loaded_specs.values. Is there some other way to do this ? -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
