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
Support for .user.ini files (PHP) #160
Comments
Hello, |
Regarding https://github.com/nginx/unit/pull/543/files#r714593715: |
We definitely don't want additional syscalls on every request. While sometimes it may be handy, but the overhead isn't worth it. |
It won't actually be updated on every request. TTL is checked on every request, and if expired, then it will be updated. But I'm mostly on side of performance. Just wanted to point out that it is a necessary trade-off if you wanna follow PHP-FPM spec... |
TTL cache may work good or not. First of all, the cache isn't shared between processes. As a result, if you have 50 processes, then it can be up to 50 scans for each entry even within TTL. If the processes configured to scale dynamically, then situation will be even worse as each process starts up with a clean cache. At the same time, I guess that if we just scan all the directory tree for |
I think it is a good approach. Reloading Unit is just a matter of doing an API call anyway... |
Ping. Hello, Cheers, Alex |
Closed due to timeout |
Hello,
.user.ini file is good for users without access to server configuration and it should allow changes only variables with PHP_INI_PERDIR/PHP_INI_ALL flags.
Now my users are using .user.ini to reconfigure their applications (php-fpm), so it will good to still have that possibility with Unit.
More about .user.ini: http://php.net/manual/en/configuration.file.per-user.php
Any chances for support for it?
The text was updated successfully, but these errors were encountered: