Skip to content
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

playbook drupal_public_filesystem_user hardcoded to Ubuntu's www-data user #793

Closed
seth-shaw-unlv opened this issue Feb 2, 2018 · 4 comments

Comments

@seth-shaw-unlv
Copy link
Contributor

seth-shaw-unlv commented Feb 2, 2018

Running the playbook internal webserver-app role fails when deploying on CentOS during the set permissions on the public files directory step. The owner and group for that step are set to a drupal_public_filesystem_user variable which is currently set in inventory to Ubuntu's Apache user "www-data".

Now, this step is the only one that uses this variable. The drupal_public_filesystem_user variable is only used for this step and I can't think of a reason why we shouldn't just use the webserver_app_user variable all the other steps use (which is also set to the Apache user, just like the drupal one). If we really wanted to keep the drupal_public_filesystem_user variable we could move this variable from group_vars into the role defaults and have it inherit the value of webserver_app_user. This would allow it to work for both Ubuntu and CentOS by default and still allow someone to set their own value group_vars if they really wanted to change it.

If no one objects, I'm willing to create the 4-line pull request.

@seth-shaw-unlv
Copy link
Contributor Author

On a related note, why doesn't the playbook's repo have its own issues tab?

@whikloj
Copy link
Member

whikloj commented Feb 5, 2018

I think none of the repos in Islandora-Devops are supposed to have issues tabs, we just forgot to turn them off. There was a decision made long ago to centralize the issues on the Islandora-CLAW/CLAW repo to keep them all in one place.

As for the actual issue, I am a 👍 to using the webserver_app_user instead of the drupal_public_filesystem_user

@dannylamb
Copy link
Contributor

Recently I've been running into issues executing functional tests on new boxes. I wonder if this is related? It'd be a good test to see if functional tests will run on the environment, since it needs to put its html output on the drupal filesystem for debugging. Right now it blows up because it's owned by ubuntu and not www-data like it should.

@seth-shaw-unlv seth-shaw-unlv changed the title playbook drupal_public_filesystem_user hardcoded to Ubuntu playbook drupal_public_filesystem_user hardcoded to Ubuntu's www-data user Feb 7, 2018
@seth-shaw-unlv
Copy link
Contributor Author

Probably not, since this was using the www-data user (as described in the initial post but not made clear by the issue title).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants