You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think, for the sake of sanity and simplicity, we should:
Ensure deploy user is a member of www-data group
Ensure www-data user is a member of deploy group
Ensure the web root is 664 for files, and 775 for directories
Ensure the web root is owned entirely by www-data (user and group)
My reasoning for the last item in particular is that many of the strangest permissions issues we've seen thus far (installing/upgrading themes & plugins) appear to be the result not of an operation being prohibited by permissions, but by flaky permission checks within the Wordpress core and plugin codebases
That last item is a good point. Using chmod g+s may be worth doing as part of the setup process. Maybe even cap's " group_writeable" flag will handle this....
Activity
EvanK commentedon Oct 29, 2013
I think, for the sake of sanity and simplicity, we should:
deployuser is a member ofwww-datagroupwww-datauser is a member ofdeploygroupwww-data(user and group)My reasoning for the last item in particular is that many of the strangest permissions issues we've seen thus far (installing/upgrading themes & plugins) appear to be the result not of an operation being prohibited by permissions, but by flaky permission checks within the Wordpress core and plugin codebases
ericclemmons commentedon Oct 29, 2013
That last item is a good point. Using chmod g+s may be worth doing as part of the setup process. Maybe even cap's " group_writeable" flag will handle this....
Various fixes for `genesis:permissions`