The next release of Capistrano will do "chmod -R g+w" on the new
release during the update_code task, which should fix group
permissions issues. Regarding the second set of directories you
indicated, those directories are all explicitly removed and then
symlinked by Capistrano on each deploy. You should be able to fix
your permission issues once by chmoding the #{shared_path} and its
contents. After that, they won't change, since the shared directory
is not touched by the deploy process.
- Jamis
> --~--~---------~--~----~------------~-------~--~----~
> To unsubscribe from this group, send email to capistrano-
> unsub...@googlegroups.com
> For more options, visit this group at http://groups.google.com/
> group/capistrano
> -~----------~----~----~----~------~----~------~--~---
>