Ryan E <ryan...@gmail.com> wrote:
> 1. You mentioned that it is a good idea to "copy the broken release to
> a safe place". Doesn't the rollback task already handle this for you?
> When I run a rollback, I end up with a
> rolled-back-release-#{last_release}.tar.gz in the deploy directory.
That doesn't happen if it's really a bad deploy.
The directory gets nuked...
My usual trick is to insert capistrano step which basically turns into either
an interactive shell, or has "sleep 10000" on it, so that I can login and
poke at things.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
--
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 capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/capistrano/10922.1414446412%40sandelman.ca.
For more options, visit https://groups.google.com/d/optout.
