4 ms·
unfortunately, matomo is harder than necessary to automatically deploy to containerized environments like heroku because they don't support the 12 factor princi
by clairity 8y ago
unfortunately, matomo is harder than necessary to automatically deploy to containerized environments like heroku because they don't support the 12 factor principles [1]. a cynic might assume that this is because it would undermine their own hosted solution.
[1] https://github.com/matomo-org/matomo/issues/6223 https://github.com/matomo-org/matomo/issues/6223
(i would use matomo if they fixed this issue)
- vorpalhex 8y agoOr they just chose a very common pattern of keeping configs in files instead and haven't gotten around to support environment variables. Probably not a conspiracy... given that you could fork it, implement this feature, and then PR it back to the main repo...
- clairity 8y agoi looked into it about a year ago, and it would have required a rewrite of the (brittle) installer as well as supporting modules (that seemed to be dependencies of other parts of the system), not just extracting the configs into environment variables (which i did, but that didn't solve the problem). non-trivial, to say the least.
- icco 8y agoWe use Matomo in containers, you can write configs with the incoming hostname and it works pretty well.