Peter, You can use setuid on the directory, to set the directory permissions at write time. Typically the way this works is you would chown the directory to deploy:www-data (assuming deploy user is a member of the www-data group). You then set `chmod g+S` on the directory (see your platform for setgid). That will ensure that your new files are written as `deploy:www-data` (deploy because that's the deploy user who is writing the file, and www-data inherited from executing a file creation in a g+S directory with the www-data group ownership)
Since the default permissions are `g+r` (group read) your www-data group, including the www-data user who runs your web server should be able to read the files. This gets more complicated if you need enable an upload directory…but one step at a time! Hope this makes some sense, permissions are tricky, and on the next major cap release, there will be strong instructions on how to set this up, with a bundled "fix perimissions" task for anyone who cant' do it our way. Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
