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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃挕 FEATURE REQUEST]: Configuration to UNIX socket permissions #1789
Comments
Hey @Starfox64 馃憢 |
Yes, I've switched to unix sockets for RPC and FastCGI, the performance increase is quite significant. In my setup I have NGINX talking to RR's FastCGI and on the PHP side I use the KV plugin as a Laravel cache store:
Side note: I was quite surprised by this, as before I was using a Redis Sentinel cluster over the network (may have been on the same node, I didn't get to verify) was even faster (~320 rqps). I think there might be some improvement oportunities in the KV implementation. |
Ah, got u @Starfox64 馃憤 |
Plugin
None
I have an idea!
Add a configuration option to set the file permissions and ownership of UNIX sockets created for RPC, FastCGI, etc.
Right now it simply uses de default umask of the system which makes the socket inaccessible to non owners.
The text was updated successfully, but these errors were encountered: