On Mon, Dec 17, 2012 at 3:28 PM, Tim Johnson tim@akwebsoft.com wrote:
- Earnie Boyd earnie@users.sourceforge.net [121217 04:24]:
On Sat, Dec 15, 2012 at 8:47 PM, Tim Johnson wrote:
But drush is still changing permissions to 750 on the root directory on the remote server. This disables the site until I reset the permissions to 755.
DocumentRoot should never be able to be read by others. Drush is doing a good thing here. The DocumentRoot group should match that of the user id executing httpd. This would allow the httpd user to read the DocumentRoot directory with 750 permissions.
According the techs at hostmonster (this is a _shared_ hosting), all site roots *must* be 755.
I also escalated my question to their upper-level techs with Ernie's statement above quoted, but have yet to get a reply.
It seems that what drush is doing is simply setting the same permissions as the source site. I.E. when I push content from my workstation where permissions are 750, then drush sets the target as 750, but when I changed the permissions on the workstation to 755, drush obliging left them at 755 on the remote hostmonster server.
I think my brain is going to explode.... after 17 years of web programming and 12 on *nix systems, I still feel like a flipping noob...
Some host companies want you to do the wrong thing. See https://my.hostmonster.com/cgi/help/594 for the suggested corrections. You're probably correct about your client and ftp. You might need to change the permissions on your client to get along with hostmonster service.