[Capistrano] Problem with basic cap invoke command

Hi everybody, I just upgraded my Rails project from Capistrano 1 to 2 and realised that the tasks using run are failing. I then RTFM and tried to break it down to the most simple case and I found that even 'cap invoke COMMAND=ls' is failing: # cap - invoke COMMAND=ls ** message *

[Capistrano] Re: Problem with basic cap invoke command

What do your Capfile and config/deploy.rb look like? Another option to increase verbosity is to turn on the SSH debugging...but that is VERY verbose, and mostly meaningless to the uninitiated. Still, you're welcome to try it: ssh_options[:verbose] = :debug You can email me the output

[Capistrano] File.exists?() in deploy.rb

in a cap task, if I 'puts File.exists?(current_path)' I get false returned! Why is that? I've got a task that creates a directory in :after_symlink. when I cap deploy, this mkdir works fine. But when I cap deploy:migrations, the mkdir fails saying that the file already exists. I added an

[Capistrano] Re: Capistrano with darcs error darcs failed: Not a repository

Thanks, though, at least I know I'm not nuts. I'll figure out a workaround, probably just upload manually for now. -Stuart On Aug 16, 4:32 pm, Jamis Buck [EMAIL PROTECTED] wrote: Sadly, yeah, it sounds like you're one of the lucky few who are getting bitten by that one. I've never been able

[Capistrano] Re: File.exists?() in deploy.rb

of course. I knew it was something simple. thanks guys. On Aug 16, 2:41 pm, Jamis Buck [EMAIL PROTECTED] wrote: Because File.exists?() tests on the local machine, and current_path exists on the remote machine. Try running that task after update_code, instead of after symlink. That way it

[Capistrano] Possible good news on the environment-variables front

Alright, I have no idea why I never picked up on this before. If you already knew this and tried to tell me, I apologize for my obtuseness. Apparently, the reason Capistrano doesn't pick up your .bashrc and such is because Capistrano allocates a pseudo-tty for each command. I'm not sure why I

[Capistrano] Re: Can I deploy a specific revision

You can deploy a specific revision by setting the revision variable. You can do this in the recipe file with set :revision, 60. Since it's the sort of thing you might not want to set permanently, you can also do something along the lines of: cap deploy -s revision=60 On Aug 9, 5:02 pm, Alan

[Capistrano] Re: Hard coded environment settings. Is this a bug?

Sure, I'd entertain a patch for that. If you whip one up, please submit it to http://dev.rubyonrails.org. Thanks! - Jamis On 8/16/07, Drinkingbird [EMAIL PROTECTED] wrote: Hi all, I've come across a situation where I needed to use a name other than 'current' for the symlink to the latest

[Capistrano] Re: Hard coded environment settings. Is this a bug?

Cheers. Patch at http://dev.rubyonrails.org/ticket/9283 - Chris On Aug 17, 10:50 am, Jamis Buck [EMAIL PROTECTED] wrote: Sure, I'd entertain a patch for that. If you whip one up, please submit it tohttp://dev.rubyonrails.org. Thanks! - Jamis On 8/16/07, Drinkingbird [EMAIL PROTECTED]