Reputation: 7099
This completely destroys any hope of using google drive for shared assets when developing. System level services such as apache do not run as the logged in user.
Permissions stick until someone else makes an edit and the updates are then synced.
Google drive, changes the permissions of directories and files to 700 and 600 respectively. This results in 503 forbidden requests in Apache or any other process not running as the logged in user.
Is there anyway to get Google Drive to stop destroying my permissions? Maybe by respecting my umask, or some option to configure it.
755 for directories and 644 for files would be much more appropriate.
Upvotes: 3
Views: 155
Reputation: 12673
Unfortunately this a product issue, and your post on the Drive Help Forum is the correct way to raise this concern.
Upvotes: 3