I''ve been trying to figure this out with my host''s support staff (Site5), and I hope this will save others some trouble... Recently, Capistrano was modified (see changelog here: http://tinyurl.com/y9szza) to apply "chmod g+w" to the entire release_path after checkout. This is good in a team environment, but bad on shared hosts (who like to restrict executable files to "user permissions only"). At the moment, my "fix" is to stick to Capistrano 1.2, and work on an updated update_code task that doesn''t run chmod (which, it seems to me, should be a separate task, anyway). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---