-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up /var/www/drupal file/dir permissions #67
Comments
My intent, that isn't fully implemented, is that fedora configs and drupal site are all owned by |
Thanks @ruebot So why not 755? As you know, my end goal is to be able to reuse the scripts with Packer and it would be better (I'm told by the sysadmins) not to have the web user be able to write to the files it serves (the exception being the 'files' dirs). I know this isn't as much of a concern on a temporary dev box that goes up and down as needed, but I'm wondering if there is a reason not to use 755(?) I also don't have a problem with 'web' being the group, but I'm curious why you didn't use www-data for it? Was there a particular reason? |
What if we made this a variable for #70? |
The user group or the permissions? I'm not sure it makes as much sense to expose the group and file permissions as variables. There will already by a lot of them and I'm more inclined to try and limit the number of variables (to avoid variable fatigue -- is that a thing? -- for people setting up the system). I'm fine with this ticket being about consistency and 775/vagrant:web are fine with me if that's what we land on... I do see this build as having a different audience from the (hypothetical) Packer build. I guess I was more interested in the reasoning (and more, in particular, the reasoning being the group choice). |
Actually, I'm not sure what I was thinking. 755 makes complete sense, and the files dir should be 775. I blame lack of sleep from jet lag 😄 |
I'd say that the Drupal directory structure at the end of the build should be owned/writeable by vagrant and be readable by the www-data group (with the exception of 'files' which needs to be writeable by the web user: www-data). Other thoughts? I see there is a "web" group that vagrant, tomcat7, and apache/www-data are in. As it is now on the file system, some things are vagrant:vagrant, some are root:root, and some are vagrant:web.
This is just to start the discussion about how we can end up with a consistent permissions scheme after installation.
The text was updated successfully, but these errors were encountered: