This is my first run through with Capistrano (v2.4.3) , so I've
followed the instructions (in "Deploying Rails Applications") and It
Doesn't Work (tm).
What's killing me is that "cap deploy:setup" creates the basic
directory structure using sudo, but then when I "cap deploy" it
doesn't bother with sudo and hence errors out saying "can't create the
directory". I get the same problem whether I use the default /u/apps/
#{application} or /home/#{user}/someplace-else.
There's an earlier thread mentioning the same problem, and the given
solution is to add "set use_sudo, :false" to deploy.rb
Which is fine if it works, but if you can never get anything to work
without this setting why is use_sudo defaulting to :true?
Either things have evolved since the instructions in "Deploying Rails
Applications" was printed or I'm missing something extremely obvious.
My setup is;-
Client server, used for development, and hosting svn. SSH to local
network staging server with a different username and password. If I
manually SSH to the staging server then I can svn export the bits I
need perfectly OK.
So I know the only problem is the permissions set up on the root
directories created by "cap deploy:setup". Should I edit the
permissions? If I have to edit them then why are they set up the way
they are? Why can't I just do "cap deploy:setup" followed by "cap
deploy"?
All comments appreciated
John Small
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
