php.ini under CustomBuild

doumu

Verified User
Joined
Aug 13, 2019
Messages
19
The new documentation here:

Points to the old docs here:

The old docs note the ability to make changes to PHP by adding a custom ini file in /usr/local/php74/lib/php.conf.d/

Is this a requirement? Rebuilding PHP doesn't seem to harm the existing php.ini file, but some updates seem to overwrite this?

Is it safe to make changes to /usr/local/phpXX/lib/php.ini if CustomBuild is in use?

What are the expected cases where CustomBuild would disturb the main php.ini file?
 
You cannot edit the system php.ini files directly they will get overwritten. You need to make any custom changes with custom files.

PS
This templating is central to all of da. 95% of the custom changes you might want need to be done with custom folders and files.

just a example
 
I appreciate that in the context of Apache and other system configs. Here the documentation is actually suggesting to edit the php.ini file directly and doesn't note the necessity of a custom file for this. Nor does it note the possibility of the core php.ini file being overwritten. Most CB controlled conf files have a warning at the top to not edit this directly and create an include/custom/etc. php.ini does not.

In the Apache conf, you see:
Code:
#######################################################################################
# Do not change anything in files below, because they are rewritten by DirectAdmin    #
#######################################################################################

Is the file being overwritten always the case?
If so, what will cause this?
If so, should the documentation be improved as nearly every DA server will have CB?

I tried to find definitive answers in old forum posts, but just found suggestions. Was hoping @smtalk could clarify this and possibly include in documentation if needed.
 
Back
Top