matomo-org / matomo-org/docker
Feature request: Don't compress Matomo within the container
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1k
- Forks
- 384
- PR merge metrics
- No merged PRs in 30d
Description
From a customer:
The container has a compressed version of matomo that it unzips on entrypoint. But docker images are always compressed so all this should be doing is making new pod startup slightly slower and introducing an extra stumbling block for running Jobs (such as the archive job) against it. If it was adjusted to just be built with the current matomo release, it'd be more standard and perform just the same.
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
Start by inspecting the Docker build and entrypoint, focusing on where the compressed Matomo release is created and unzipped. Update the image to use the current Matomo release directly, then verify normal container startup and archive Jobs no longer depend on runtime decompression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100