docker
docker copied to clipboard
matomo-org
custom database configuration
For migration cases, it would be nice to support custom variables, as known from https://github.com/ecobytes/docker-piwik/tree/nossl#getting-started
We'll probably want to align both images around some Alpine core.
Which variable do you miss?
Feel free to PR :)
And yes alpine would be nice :)
Related to https://github.com/piwik/piwik/issues/10914
@pierreozoux I miss being able to provide the database setup. As mentioned in piwik/piwik#10914 if I have an ephemeral filesystem or setup as a kubernets pod I would like to be able to provide the database config and admin data as parameters to the deployment.
@vfbsilva If you have already any work related to k8s, https://github.com/piwik/docker-piwik/issues/62 :)
@pierreozoux config maps state:
The ConfigMap API resource holds key-value pairs of configuration data that can be consumed in pods or used to store configuration data for system components such as controllers. ConfigMap is similar to Secrets, but designed to more conveniently support working with strings that do not contain sensitive information.
And I do want to store my database password. Seems risky. #62 seems a much better approach. Because config maps and secrets rely the idea that I can use some state-full data storage. For instance, lets imagine I will deploy a piwik for each system the company runs passing the variables as arguments simplifies my life when using tools like jenkins.
I now also understand that piwik will ask for the database credentials upon first run. Yet this may introduce security risks upon deployment, why automatic configuration injection may be preferred. Currently a known option is
https://github.com/indiehosters/piwik/blob/master/docker-compose.yml#L20-L21
Some ENVs are supported through plugins (https://github.com/matomo-org/matomo/issues/10914) but there is no real CLI installation support: https://github.com/matomo-org/matomo/issues/10257
