github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-15 23:02:03 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[PR #765] feat: add Matomo blueprint #11510

New Issue
Open
opened 2026-06-11 01:37:40 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-11 01:37:40 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/765
Author: @SamirChatwiti
Created: 4/1/2026
Status: 🔄 Open

Base: canary ← Head: canary

📝 Commits (8)

  • bd83cb9 feat: add Matomo blueprint
  • 9b3745f feat: add Matomo blueprint (v2 - fixed bot issues)
  • 5945e44 feat: finalize Matomo blueprint with official schema
  • ad24b4e feat: match official compose standards for Matomo
  • f6b18ca feat: finalize Matomo blueprint with fixed schema and logo
  • da9c076 feat: sort Matomo entry alphabetically in meta.json
  • f2428bc feat: finalize Matomo blueprint with sorted meta and flat variables
  • d70f45f feat: finalize Matomo with sorted tags

📊 Changes

4 files changed (+69 additions, -0 deletions)

View changed files

➕ blueprints/matomo/docker-compose.yml (+29 -0)
➕ blueprints/matomo/matomo.png (+0 -0)
➕ blueprints/matomo/template.toml (+22 -0)
📝 meta.json (+18 -0)

📄 Description

What is this PR about?

New PR of Matomo Template.

Checklist

  • I have read the suggestions in the README.md file
  • I have tested the template in my instance
  • I have added tests that demonstrate that my correction works

Issues related

Adds Matomo one-click deployment.

Greptile Summary

This PR adds a Matomo web analytics blueprint for one-click deployment via Dokploy. The docker-compose.yml is mostly well-structured (correct version, health-checked MariaDB, named volumes, no ports/container_name/networks), but there are two blocking issues in template.toml and one in meta.json that need to be resolved before this template will work correctly.

Key issues found:

  • template.toml schema is incorrect (P1): The file uses a [[variables]] array-of-tables format with name/label/defaultValue/placeholder keys — a schema used by no other blueprint in the repo. Every other template uses a flat [variables] table (key = value) plus a [config] block with an env array and [[config.domains]] for routing. Without the [[config.domains]] section, Dokploy won't configure the Traefik reverse-proxy route for the service.
  • Hardcoded default credentials (P1): Both DATABASE_ROOT_PASSWORD and DATABASE_PASSWORD default to literal placeholder strings. Per AGENTS.md, secrets must use Dokploy's built-in helpers so each deployment receives unique credentials.
  • Version mismatch in meta.json (P1): \"version\": \"latest\" does not match the pinned image tag matomo:5.1-apache in docker-compose.yml. AGENTS.md requires these to match exactly.
  • Logo format (P2): AGENTS.md prefers SVG logos; a PNG is provided.

Confidence Score: 2/5

Not safe to merge — the template.toml uses an unsupported schema and is missing the domain-routing section, making the template non-functional as submitted.

Three P1 issues: wrong template.toml format (unsupported schema + missing config.domains), hardcoded credentials that violate the project's explicit security policy, and a version mismatch in meta.json. All three are straightforward to fix but must be addressed before the template can be used reliably in Dokploy.

blueprints/matomo/template.toml needs a full rewrite to match the standard schema. meta.json needs the version field corrected.

Reviews (1): Last reviewed commit: "feat: add Matomo blueprint (v2 - fixed b..." | Re-trigger Greptile

Greptile also left 4 inline comments on this PR.

(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!

Context used:

  • Context used - AGENTS.md (source)

🔄 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/765 **Author:** [@SamirChatwiti](https://github.com/SamirChatwiti) **Created:** 4/1/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `canary` --- ### 📝 Commits (8) - [`bd83cb9`](https://github.com/Dokploy/templates/commit/bd83cb9fd0e126b77152520d63fe887c6cd4bbc0) feat: add Matomo blueprint - [`9b3745f`](https://github.com/Dokploy/templates/commit/9b3745f9194696554b29d64c775b16b49cdcefc1) feat: add Matomo blueprint (v2 - fixed bot issues) - [`5945e44`](https://github.com/Dokploy/templates/commit/5945e44c7c60eec566ee7eb2ade8335bcc2622d3) feat: finalize Matomo blueprint with official schema - [`ad24b4e`](https://github.com/Dokploy/templates/commit/ad24b4e71b4676cb97fba47abbe8fe36bafe4606) feat: match official compose standards for Matomo - [`f6b18ca`](https://github.com/Dokploy/templates/commit/f6b18cae8a294518cfe70fa75a83a850cd699b55) feat: finalize Matomo blueprint with fixed schema and logo - [`da9c076`](https://github.com/Dokploy/templates/commit/da9c076713e74f6642f03775cd22272e5b3b266f) feat: sort Matomo entry alphabetically in meta.json - [`f2428bc`](https://github.com/Dokploy/templates/commit/f2428bc788e271cd574317d86684ed99a2c59bb1) feat: finalize Matomo blueprint with sorted meta and flat variables - [`d70f45f`](https://github.com/Dokploy/templates/commit/d70f45f1c9865c0f888143625015b3bc1f1bd6bb) feat: finalize Matomo with sorted tags ### 📊 Changes **4 files changed** (+69 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/matomo/docker-compose.yml` (+29 -0) ➕ `blueprints/matomo/matomo.png` (+0 -0) ➕ `blueprints/matomo/template.toml` (+22 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description ## What is this PR about? New PR of Matomo Template. ## Checklist - [x] I have read the suggestions in the README.md file - [x] I have tested the template in my instance - [x] I have added tests that demonstrate that my correction works ## Issues related Adds Matomo one-click deployment. <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a Matomo web analytics blueprint for one-click deployment via Dokploy. The `docker-compose.yml` is mostly well-structured (correct version, health-checked MariaDB, named volumes, no `ports`/`container_name`/`networks`), but there are two blocking issues in `template.toml` and one in `meta.json` that need to be resolved before this template will work correctly. **Key issues found:** - **`template.toml` schema is incorrect (P1):** The file uses a `[[variables]]` array-of-tables format with `name`/`label`/`defaultValue`/`placeholder` keys — a schema used by no other blueprint in the repo. Every other template uses a flat `[variables]` table (key = value) plus a `[config]` block with an `env` array and `[[config.domains]]` for routing. Without the `[[config.domains]]` section, Dokploy won't configure the Traefik reverse-proxy route for the service. - **Hardcoded default credentials (P1):** Both `DATABASE_ROOT_PASSWORD` and `DATABASE_PASSWORD` default to literal placeholder strings. Per `AGENTS.md`, secrets must use Dokploy's built-in helpers so each deployment receives unique credentials. - **Version mismatch in `meta.json` (P1):** `\"version\": \"latest\"` does not match the pinned image tag `matomo:5.1-apache` in `docker-compose.yml`. `AGENTS.md` requires these to match exactly. - **Logo format (P2):** `AGENTS.md` prefers SVG logos; a PNG is provided. <h3>Confidence Score: 2/5</h3> Not safe to merge — the template.toml uses an unsupported schema and is missing the domain-routing section, making the template non-functional as submitted. Three P1 issues: wrong template.toml format (unsupported schema + missing [[config.domains]]), hardcoded credentials that violate the project's explicit security policy, and a version mismatch in meta.json. All three are straightforward to fix but must be addressed before the template can be used reliably in Dokploy. blueprints/matomo/template.toml needs a full rewrite to match the standard schema. meta.json needs the version field corrected. <sub>Reviews (1): Last reviewed commit: ["feat: add Matomo blueprint (v2 - fixed b..."](https://github.com/dokploy/templates/commit/9b3745f9194696554b29d64c775b16b49cdcefc1) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27017341)</sub> > Greptile also left **4 inline comments** on this PR. <sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</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>
GiteaMirror added the pull-request label 2026-06-11 01:37:40 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#11510
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?