BTW: It is not possible for me to edit
/etc/e-smith/templates/opt/remi/phpxx/root/etc/php.ini
As it is not a normal file - it seam to redirect to a template folder???
As Janet said, read the documentation on templates. That directory contains the template fragments that generate the file.
So normally the template fragments would expand the file /opt/remi/phpxx/root/etc/php.ini
However, just to complicate things even further, you will notice that the file /opt/remi/phpxx/root/etc/php.ini doesn't actually exist.
When you modify the SCL PHP template fragments and re expand the file via signal-even php-update it actually expands to:
/etc/opt/remi/php71/php.ini
(I have no idea why)
I suggest you copy the dir
/etc/e-smith/templates/opt/remi/php71/root/etc/php.ini
over to
/etc/e-smith/templates-custom/opt/remi/php71/root/etc/php.ini
And then start looking at the fragments (files) in the custom directory.
You probably want to adjust this:
[root@esmith php.ini]# cat 80ModuleSettings03Debugger
[Debugger]
debugger.host = localhost
debugger.port = 7869
debugger.enabled = False
Now, if you want to get to be a really cool cat you can actually add yourself a bit of code and key to easily enable/disable this
[Debugger]
debugger.host = localhost
debugger.port = 7869
debugger.enabled = {
my $debug = $php71{Debugger} || "False";
$OUT .= "$debug";
}
signal-event php-update and check the php.ini file and it should default to False.
config setprop php71 Debugger True
Then signal-event php-update again.
See what happens.