Make php socket accessible for webserver group #426
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks bro! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Make php socket accessible for webserver group
In the current setup the user/group who owns the php-fpm socket is always identical to the user that is used to run the php-fpm processes (either zabbix_php_fpm_conf_user or zabbix_web_conf_web_user).
This produces an broken setup, as nginx/apache are running as different users (
www-dataon Debian), so they are not able to access the socket.Fixes: #425
I'm not entirely sure if this patch is really the nicest way to handle this, as now the user is no longer able to override the owner of the socket from a group var.
ISSUE TYPE
COMPONENT NAME
zabbix-web