Actually after making this suggestion I ran into an more granular issue.
If one uses the PHP Settings section to configure those values - they will be only available to the PHP-FPM pool, but not to command line execution from cron jobs or manual.
To get around this would be to have the php.ini settings file stored somewhere in the application file structure so one can pass it to the php executable via -c option
As to how much value it provides to users. I think truly it only provides an ease of access, but not an overall improvement.
Alex
Thank you for your response.
Actually after making this suggestion I ran into an more granular issue.
If one uses the PHP Settings section to configure those values - they will be only available to the PHP-FPM pool, but not to command line execution from cron jobs or manual.
To get around this would be to have the php.ini settings file stored somewhere in the application file structure so one can pass it to the php executable via -c option
As to how much value it provides to users. I think truly it only provides an ease of access, but not an overall improvement.