And checking the symlink commands being executed during deployment, I can see the current release path being used is different from the current release on the server
On Wednesday, 23 January 2013 17:26:17 UTC, bsod99 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] * 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 --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
