I'm successfully running Capistrano deploys and have noticed that the
releases build up fairly quickly when in development, so I run cap
deploy:cleanup to keep the number of releases that actually exist on
the server to the default of 5, but I also noticed something else...

All the assets for each release are symlinked to the same shared
directory.

First, is there a reason for this? I intend to precompile new assets
on each deploy, so is there really a benefit? Is there a way to turn
this off and store assets with the releases?

Second, the cap deploy:cleanup doesn't cleanup the assets, so my
shared/assets folder is growing rapidly, is there a reason I can't
just have the assets precompile into the actual assets folder inside
the release, and ditch the symlinked assets business?

This question is also posted here incase anyone is an avid
StackOverflow User : http://stackoverflow.com/q/8507325/555384

-- 
* 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

Reply via email to