Description
We broke the zero-maintenance property of this project by keeping a static copy of the config.docker-template.php on the project.
We do this in order to set a right value for the cookie prefix on multiple-instance mode.
This is not good at all, since we don't want to maintain a copy of the config.docker-template.php file on this project.
Since every time this file is changed it can potentially make this project don't work and makes more difficult its maintenance.
Details
When using the multiple instance feature, we use a custom template (config.docker-template.php) for the config.php file for each Moodle instance based on the template provided by moodle-docker
project.
Why we decided to add a custom static config template?
We add a different prefix for moodle cookies to avoid conflicts between each instance. This configuration isn't present in moodle-docker template. For this reason, we added a custom template.
We decided to configure the template statically instead of dynamically because we need to add the cookies configuration in a specific line of the file.
Possible issues:
If moodle-docker
project modifies this template configuration file, we will have to update our template manually. The decision of having a custom template file broke the characteristic of wiris-moodle-docker
being zero maintainable project.
Expected result
Find the way to add dynamically the cookies prefix for each moodle instance.