Browse files

[asset pipeline] Update Capistrano info

v2.8.0 of Capistrano has a recipe to handle precompile
and symlinking.
  • Loading branch information...
1 parent dbf2256 commit b840d71bfb702b121b48832f984090e202793f10 @rhulse rhulse committed with fxn Aug 6, 2011
Showing with 4 additions and 6 deletions.
  1. +4 −6 railties/guides/source/asset_pipeline.textile
@@ -276,17 +276,15 @@ The rake task is:
rake assets:precompile
-You can run this as part of a Capistrano deployment:
+Capistrano (v2.8.0+) has a recipe to to handle this in deployment. Add the following line to +Capfile+:
-before 'deploy:symlink' do
- run "cd #{release_path}; RAILS_ENV=#{rails_env} rake assets:precompile"
+load 'deploy/assets'
-If you are not precompiling your assets, and you are using the default cache file store (which is the file system), you will need to symlink +rails_root/tmp/cache/assets+ from the shared folder that is part of the Capistrano deployment structure in order to persist the cached file between deployments.
+This links the folder specified in +config.assets.prefix+ to +shared/assets+. If you already use this folder you'll need to write your own deployment task.
-TODO: Extend above task to allow for this and add task to set it up (See commits 8f0e0b6 and 704ee0df). Note: Capistrano folks are working on a recipe - update this when it available (see
+It is important for this folder is shared between deployments so that remotely cached pages that reference the old compiled assets still work for the life of the cached page.
The default matcher for compiling files will include +application.js+, +application.css+ and all files that do not end in +js+ or +css+:

0 comments on commit b840d71

Please sign in to comment.