On Feb 28, 4:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> In my case, it proved to be that my deployment user lacked sufficient
> permissions in the top-level folder where I was trying to put the
> project. I'd love to know what permissions I *should* use, but as this
> is on an internal test server I just said the heck with it and relaxed
> them to 777 and all was well. No doubt there's a more elegant (or at
> least more secure!) solution.
What I do:
1) Create a user www and a group www on my deployment server. This is
the same user and group as my webserver use.
2) Add the users that I use for deployment to the www group.
3) sudo chown -R www:www #[deploy_to} <= This could be added to the
setup task
Then my deployment users have proper permission to write to the
release directory.
Then, in post_symlink I do
4) sudo "chown -R www:www #{release_path}"
HTH
--
Ray
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
