Conversation
|
Why do we need a ConfigMap with the content of the |
|
The starter script copies the config.dist.php to config.php. This way the config can be pre-populated by setting them in dist file before the copy to config. I could add that this is not mandatory. See here Line 60 in a8155e9 |
|
I explained it and marked it optional. |
|
I keep copy of the working config.php, and thus can start from fresh install at any time. It's useful for that. While having db dump saved also of course. |
|
You wrote For your information, all the settings in config.php can be overridden by their associated LB_XXX environment variables, as you can see in file By the way, could Kubernetes/openshift be configured to use the environment file In parallel, I am re-writing the docker part to have the .examples directory consistent with the new content. |
|
Ah, I thought it's only the small subset of env variables used at examples. I recall I saw something mentioning it at some point now that you say. It doesn't even need to be in configMap, they can be directly in the deployment file. I will remove the configMap and give an example of setting them in deployment config. I personally avoid using env vars for anything secret. I've seen many apps dump it's env to browser when they crash. I wonder if that can happen with php? Anyhow, perhaps this is just personal bad memory. I'll push the changes soon. |
|
That was good idea, thanks. Example is cleaner this way. |
Kube example for #142