matomo-org / matomo-org/docker
Requesting a document that explains how to update Matomo app running on container images
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1k
- Forks
- 384
- PR merge metrics
- No merged PRs in 30d
Description
Hi, can you provide a document that describes how to update a Matomo app running on a container image?
My particular case: I am running Matomo fpm-alpine on an EKS cluster + RDS.
I went from `matomo:5.1.2-fpm-alpine` to `matomo:5.2.2-fpm-alpine` and the UI still requested me to click on the update button.
There is no documentation about how to update a Matomo container using a new image, the closest I could find is this:
https://matomo.org/faq/on-premise/update-matomo/
Imho, his does not make sense, it says it will download new files which we dont need because I already updated the image.
Also, please consider automation/scripting ways of doing it, having to click on a button after updating Matomo docker image breaks CI/CD concept.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository file or test; start with the linked Matomo update FAQ and the fpm-alpine version transition described here. Document the container-image update workflow, including the required UI or scripted step for CI/CD, and cover the EKS plus RDS case. Done means a user can follow the documented procedure without guessing whether files must be downloaded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, kubernetes
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100