I should have been a little more descriptive.
The problem occurs when the boxes are loaded. They tend to hang when puts
are attempted.
On 1/8/07, Mike Bailey [EMAIL PROTECTED] wrote:
I tested using 'put' on one of my CentOS boxes (centos 4) and it
worked fine.
I have included the task I
Hey Charles-
Cool I'm glad you like it. It definitely needed a cleanup of the
params and your patch looks really nice. Unfortunately email ate the
formatting and I can't use it :/ Can you send me a copy of the entire
file in its new state? You can send it to me directly if you
Yes, after setting up everything I have finally tested my deploy.rb
with local_perforce.rb and it works!
Thank you so much, you are a life saver.
I think other people who are having similar problems can use this patch
easily.
Julie
--~--~-~--~~~---~--~~
To
hj
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
If anyone has input, help would be greatly appreciated! :-) Here is
what I know:
-cap setup worked--I see the created folders on the server. This
means the ssh connection works. I see command finished.
-cap update_code, or any task it is a part of, fails. The message is
as seen below. It
I'm guessing you've got svn installed in some non-standard location.
Note that the ssh session that cap uses does NOT use the same PATH
environment variable you get when you login with an interactive
shell. It gets a bare-minimum PATH, usually just /usr/bin and one or
two others. If svn
