Thanks for all the replies. I followed dbray's advice and kept releases at, and adjusted sequencing to:
after "deploy:update", "deploy:symlink_shared" after "deploy:restart", "deploy:cleanup" This seems to be working fine (and makes sense, having thought through more carefully about what each is doing) On Thursday, 24 January 2013 02:42:51 UTC, dbray wrote: > > Keep releases should be 2 at minimum in my opinion > > On Jan 23, 2013, at 9:26 AM, bsod99 <[email protected] <javascript:>> > wrote: > > I followed the advice in another post about how to clean up old capistrano > releases, however, i've realised that the way I've implemented this has > messed up the paths in my application (just on a staging site thankfully!). > I am using the code below in my config/deploy/staging.rb script, but it > can't be running at the correct point, as after deployment I end up with > application failing as it's trying to load classes from earlier releases. > If I remove the keep_releases line and the one below, and redeploy, > everything works again. Has anyone come across this issue? > > set :use_sudo, false > set :keep_releases, 1 > after "deploy:update", "deploy:cleanup" > > namespace :deploy do > task :symlink_shared do > // run some commands i need > end > end > > before "deploy:restart", "deploy:symlink_shared" > > -- > * You received this message because you are subscribed to the Google > Groups "Capistrano" group. > * To post to this group, send email to [email protected]<javascript:> > * To unsubscribe from this group, send email to > [email protected] <javascript:> For more options, visit > this group at http://groups.google.com/group/capistrano?hl=en > > -- * 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
