On 9/18/13 7:42 PM, Ian Morcott wrote:
I tried the command... However, as the deploy was rolled back the
release was not there. :(
While it can be annoying to do so, one option for debugging this sort of
thing that I use (with cap2) is the "-d" flag to capistrano. For
instance: "cap deploy -d".
This will make cap go through it's steps by one by one, at each step
asking you for confirmation to keep going. Then, one thing you can do
is pause at the step that's failing, open up another shell, log into the
same server with the same account and the same environment, and execute
the thing cap was going to do manually, to figure out exactly why it's
failing and what needs to change for it to succeed.
(Hmm, this would actually be a useful enhancement to cap "-d" debug; at
the prompt for a step asking if cap should continue or not, there could
be an option that drops you into a shell somehow.)
--
--
* 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.
