thanks, andreas. i didn't know that the file was created. so that is somewhat helpful. but I'm more looking for how to track changes to it over time . . . like the config report does . . . Moodle's default config and log and live reports track changes as to who did what when . . .
I only see $settings->add(
new admin_setting_configtext(
'cachestore_redis/test_server',
get_string('test_server', 'cachestore_redis'),
get_string('test_server_desc', 'cachestore_redis'),
'',
PARAM_TEXT,
16
)
);
$settings->add(
new admin_setting_configpasswordunmask(
'cachestore_redis/test_password',
get_string('test_password', 'cachestore_redis'),
get_string('test_password_desc', 'cachestore_redis'),
''
)
for redis test server. None of the others have this. So it appears that there is no config_write to track the old and new value changes in the config table/report. Since these are admin configs it would be helpful.
new admin_setting_configtext(
'cachestore_redis/test_server',
get_string('test_server', 'cachestore_redis'),
get_string('test_server_desc', 'cachestore_redis'),
'',
PARAM_TEXT,
16
)
);
$settings->add(
new admin_setting_configpasswordunmask(
'cachestore_redis/test_password',
get_string('test_password', 'cachestore_redis'),
get_string('test_password_desc', 'cachestore_redis'),
''
)
for redis test server. None of the others have this. So it appears that there is no config_write to track the old and new value changes in the config table/report. Since these are admin configs it would be helpful.
Hi,
how many moodle server(cluster) do you've ?
If you've more than one and the muc is shared take care or your config.php can be rewrite with an older version by one of the server.
When I said to take care protect it with a read only and root as owner...
The best is that all cluster have is own directory for the config file.
The file can be modified from the UI of Moodle so it's out of the box.
Hope it's help.
Thanks Dominique. We have 2 Moodle "code" servers and moodledata rests on a mount share that both of the servers read/write to etc. I appreciate your advice.
I assume by your answer you are saying that there is no way right now to track the changes in the config report or through the db table for config_plugins (other than putting a trigger on it).