I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Issues related (if applicable)
Close automatically the related issues using the keywords: closes #ISSUE_NUMBER
Screenshots or Videos
Greptile Summary
This PR adds a new Matomo analytics one-click deployment template for Dokploy, consisting of a docker-compose.yml with a matomo service backed by a MariaDB db service, a template.toml for variable and domain configuration, a logo, and a meta.json entry. The overall structure is sound — healthcheck, named volumes, dependency ordering, and env-var wiring are all present — but there are a few issues to address before merging:
Broken GitHub link (meta.json): The repository URL references matomo-software/matomo, which is not the official organization. The correct URL is https://github.com/matomo-org/matomo.
Unpinned image tag (docker-compose.yml): matomo:latest should be replaced with a specific version tag (e.g. 5.3) per the project's Docker image pinning requirements; the meta.json\"version\" field should be updated to match.
Missing version: \"3.8\" (docker-compose.yml): The project style guide mandates version: \"3.8\" at the top of every compose file.
Root and app user share the same DB password: A separate root password variable would limit credential blast radius if the app is compromised.
Confidence Score: 4/5
Mostly safe to deploy, but the broken GitHub link and unpinned image should be fixed before merging.
One P1 finding (incorrect GitHub organization URL resulting in a dead link) and two P2 findings (missing compose version field and unpinned image) need to be addressed. The core deployment logic — healthcheck, volumes, env-var wiring, domain config — is correct and functional. Once the GitHub URL and image tag are corrected, this template is ready to merge.
meta.json (wrong GitHub URL) and blueprints/matomo/docker-compose.yml (missing version field, unpinned image tag).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/764
**Author:** [@sanadidari](https://github.com/sanadidari)
**Created:** 4/1/2026
**Status:** ❌ Closed
**Base:** `canary` ← **Head:** `canary`
---
### 📄 Description
## What is this PR about?
New PR of [Template Name]
## Checklist
Before submitting this PR, please make sure that:
- [ ] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [ ] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [ ] I have added tests that demonstrate that my correction works or that my new feature works.
## Issues related (if applicable)
Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER`
## Screenshots or Videos
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new Matomo analytics one-click deployment template for Dokploy, consisting of a `docker-compose.yml` with a `matomo` service backed by a MariaDB `db` service, a `template.toml` for variable and domain configuration, a logo, and a `meta.json` entry. The overall structure is sound — healthcheck, named volumes, dependency ordering, and env-var wiring are all present — but there are a few issues to address before merging:
- **Broken GitHub link** (`meta.json`): The repository URL references `matomo-software/matomo`, which is not the official organization. The correct URL is `https://github.com/matomo-org/matomo`.
- **Unpinned image tag** (`docker-compose.yml`): `matomo:latest` should be replaced with a specific version tag (e.g. `5.3`) per the project's Docker image pinning requirements; the `meta.json` `\"version\"` field should be updated to match.
- **Missing `version: \"3.8\"`** (`docker-compose.yml`): The project style guide mandates `version: \"3.8\"` at the top of every compose file.
- **Root and app user share the same DB password**: A separate root password variable would limit credential blast radius if the app is compromised.
<h3>Confidence Score: 4/5</h3>
Mostly safe to deploy, but the broken GitHub link and unpinned image should be fixed before merging.
One P1 finding (incorrect GitHub organization URL resulting in a dead link) and two P2 findings (missing compose version field and unpinned image) need to be addressed. The core deployment logic — healthcheck, volumes, env-var wiring, domain config — is correct and functional. Once the GitHub URL and image tag are corrected, this template is ready to merge.
`meta.json` (wrong GitHub URL) and `blueprints/matomo/docker-compose.yml` (missing version field, unpinned image tag).
<sub>Reviews (1): Last reviewed commit: ["feat: add Matomo one-click deployment te..."](https://github.com/dokploy/templates/commit/d4f51e874177be142de81af2569d4f6c32ee9e65) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27015413)</sub>
> Greptile also left **4 inline comments** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/764
Author: @sanadidari
Created: 4/1/2026
Status: ❌ Closed
Base:
canary← Head:canary📄 Description
What is this PR about?
New PR of [Template Name]
Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Close automatically the related issues using the keywords:
closes #ISSUE_NUMBERScreenshots or Videos
Greptile Summary
This PR adds a new Matomo analytics one-click deployment template for Dokploy, consisting of a
docker-compose.ymlwith amatomoservice backed by a MariaDBdbservice, atemplate.tomlfor variable and domain configuration, a logo, and ameta.jsonentry. The overall structure is sound — healthcheck, named volumes, dependency ordering, and env-var wiring are all present — but there are a few issues to address before merging:meta.json): The repository URL referencesmatomo-software/matomo, which is not the official organization. The correct URL ishttps://github.com/matomo-org/matomo.docker-compose.yml):matomo:latestshould be replaced with a specific version tag (e.g.5.3) per the project's Docker image pinning requirements; themeta.json\"version\"field should be updated to match.version: \"3.8\"(docker-compose.yml): The project style guide mandatesversion: \"3.8\"at the top of every compose file.Confidence Score: 4/5
Mostly safe to deploy, but the broken GitHub link and unpinned image should be fixed before merging.
One P1 finding (incorrect GitHub organization URL resulting in a dead link) and two P2 findings (missing compose version field and unpinned image) need to be addressed. The core deployment logic — healthcheck, volumes, env-var wiring, domain config — is correct and functional. Once the GitHub URL and image tag are corrected, this template is ready to merge.
meta.json(wrong GitHub URL) andblueprints/matomo/docker-compose.yml(missing version field, unpinned image tag).Reviews (1): Last reviewed commit: "feat: add Matomo one-click deployment te..." | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.