|
Permissions and remote_cache: msg#00159lang.ruby.capistrano.general
Hi all, I've been using capistrano since it came out, and always found myself very comfortable. Today I was deploying to a shared host, when I discovered I couldn't get my app to work because permissions were wrong. Instead of 644 I was getting 664 even if :group_writeable was false. I discovered that the problem happened during remote_cache's checking out and updating, it got the files from subversion with g+w permissions and even with :group_writeable set to false I couldn't do anything. So I browsed through cap's sources and saw that in deploy:setup cap set a umask of 02 before creating the paths. I did the same in remote_cache.rb and everything works fine. Do you think it's appropriated to do a umask there? Or should I avoid messing with permissions at that stage and just use some task to fix permissions after? |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: not aborting on command failure - batching hosts: 00159, Mislav Marohnić |
|---|---|
| Next by Date: | Re: Interesting Error - No space: 00159, kent.langley-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx |
| Previous by Thread: | Interesting Error - No spacei: 00159, kent.langley-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx |
| Next by Thread: | Time Sync and the local machine: 00159, Mark Percival |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |