Change php.ini from UI

Hello,

I searched in the forum but i dont see anything about it. So i add a domain for mu friends and he ask how he can edit a php.ini? That its possible to do it from UI? or all the time a need to change manually from /etc/php7.4/php.ini

10x

It needs to be done via the admin account. Depending on what need to be changed this can also be done via a template. More information needed.

Any direction how to do everything alone ?
What you mean via template ? Under domain PHP-FMP template it`s set a PHP7.4 ?

and what info you are needed ?

Check https://server.nl:8083/edit/server/php-fpm/

But what changes are need to be made?

@eris most of used :

max_execution_time
max_input_time
memory_limit
post_max_size
upload_max_filesize

I think you know that Wordpress or PrestaShop want to be change and did`t like default settings

Those can be via

https://dev.nl:8083/edit/server/php-fpm/

@eris Nice! but a little bit confused , i didt see that option in User Interface like a normal user, and the user didt know how to set it.

will be nice if that setting to be an visible place UI.

It is in the “Server” page see the “Cogs” has been changed due to the list getting to small. For the User editing we don’t allow it because it could crash the server…

As these changes will affect the server globally (meaning for all users), I recommend either use different php-fpm templates as has already been suggested or look into using .user.ini files within the docroot folders.

2 Likes

@falzo can you give a more details about our suggestion?

With apache2 and mod_php you could use things like php_admin_value in custom vhost configs or even .htaccess rules. As we use php-fpm instead you can do similar things with a .user.ini file.
I recommend do some reading about on php.net or check google for some how to :wink:

1 Like

@falzo , i didt see in Template mod_php, its possible to be a “socket” ?

For mod_php you need to over write the apache2 templates.

For example

@All that’s the difference between having php as php module vs running it as extra service that needs to connect through a socket or port.

mod_php integrates php into apache, that’s why you then can control settings from .htaccess for instance.
There are other drawbacks instead, like only one php version can be run as module and you’ll have it in every apache process spawned etc.

As mentioned above, with php-fpm you can either create your own templates to allow different settings or use a .user.ini per web-page, maybe start here to get the idea: https://www.gearhost.com/documentation/how-to-configure-user-ini

You probably could deploy something preset into the users public-html and have it owned by root, if you’d want to protect it from changes, however be aware that some software automatically can detect the way of php is connected and may want to create it’s own .user.ini files (wordfence comes to mind)

3 Likes