On Feb 6, 11:37 pm, Jamis Buck <[email protected]> wrote: > It's actually _because_ it created them with sudo that it cannot > access them. I really hate deploy:setup, actually, because I don't > know how to make it work as expected for the general case. Either you > use sudo, and then manually set the permissions on the directories, or > you don't use sudo, and make sure the parent directory has the > necessary perms BEFORE you run the task... > > At any rate, the fix is to manually correct the permissions. > > - Jamis
Thanks for the quick response, Jamis. As I use Capistrano over the next week, I'll put some time into thinking about how this might be improved. Cheers, Nick --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
