New Version

[Siumauricio]

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 Summary

This is a large bulk update PR touching 72 files — adding ~20 new blueprints and updating ~15 existing ones with version bumps, dependency fixes, and structural improvements. While many individual changes are sound (convex ports→expose fix, budibase/appsmith/grafana version bumps, supabase CONTAINER_PREFIX fix), the sheer scale of changes introduces numerous violations of the project's AGENTS.md conventions that need to be resolved before merging.

Critical issues requiring fixes:

• ports directive used in 4 blueprints (ipfs, trilium-next, verdaccio, vikunja) — this is explicitly forbidden; use expose + [[config.domains]] instead. The vikunja case is a regression.
• container_name: wg-easy added to wg-easy/docker-compose.yml — explicitly forbidden.
• Service name mismatches: wuzapi-server (folder: wuzapi) and trilium_next (folder: trilium-next) — must match exactly.
• Absolute host bind mounts in trilium-next (~/trilium-data, /etc/timezone, /etc/localtime) — forbidden per AGENTS.md.
• Version mismatches: mediafetch image uses latest but meta.json says 1.1.1; evolutionapi image changed to latest but meta.json still shows v2.1.2.
• Non-deterministic image references in postgres-pgdog (${PGDOG_IMAGE}, ${POSTGRES_IMAGE}) — images must be pinned to specific versions.
• Broken vikunja healthcheck: CMD-SHELL array form with env vars that won't be shell-substituted.
• Missing restart policy on verdaccio and openclaw main service.
• Missing version: "3.8" in openclaw, seaweedfs, strapi, and trilium-next.

Confidence Score: 1/5

• Not safe to merge — multiple new blueprints have critical convention violations and functional bugs that would break Dokploy deployments.
• There are 10+ distinct violations of the mandatory AGENTS.md conventions across multiple files: forbidden ports directives (4 files), forbidden container_name (1 file), service naming mismatches (2 files), absolute host bind mounts (1 file), version mismatches between meta.json and image tags (2 files), non-deterministic image references (1 file), a broken healthcheck (1 file), missing restart policies (2 files), and missing version: "3.8" declarations (4 files). Many of these would cause actual deployment failures in Dokploy.
• blueprints/ipfs/docker-compose.yml, blueprints/trilium-next/docker-compose.yml, blueprints/verdaccio/docker-compose.yml, blueprints/vikunja/docker-compose.yml, blueprints/wg-easy/docker-compose.yml, blueprints/wuzapi/docker-compose.yml, blueprints/mediafetch/docker-compose.yml, blueprints/evolutionapi/docker-compose.yml, blueprints/postgres-pgdog/docker-compose.yml, blueprints/openclaw/docker-compose.yml

Comments Outside Diff (8)

1. General comment

   ports directive forbidden by project conventions

   Per AGENTS.md, ports must never be included in Dokploy blueprints — Dokploy handles routing via its own ingress. This same violation appears in several other files in this PR:

   • blueprints/ipfs/docker-compose.yml lines 11–14
   • blueprints/trilium-next/docker-compose.yml lines 11–17
   • blueprints/verdaccio/docker-compose.yml lines 8–9
   • blueprints/vikunja/docker-compose.yml lines 14–15 (regression — previously used expose)

   Replace ports with expose in all of these files and configure routing through template.toml [[config.domains]] entries instead.

   Context Used: Rule from dashboard - AGENTS.md (source)

2. General comment

   container_name forbidden by project conventions

   AGENTS.md explicitly states that container_name must never be included in Dokploy blueprints, as it can conflict with Dokploy's internal container management.

   (Remove the container_name: wg-easy line entirely.)

   Context Used: Rule from dashboard - AGENTS.md (source)

3. General comment

   Service name must match blueprint folder name

   AGENTS.md requires that the primary service name exactly matches the blueprint folder name. The folder is wuzapi but the service is named wuzapi-server. This mismatch will cause Dokploy domain routing (configured in template.toml with serviceName = "wuzapi-server") to be inconsistent with the convention.

   Context Used: Rule from dashboard - AGENTS.md (source)

4. General comment

   Service name must match blueprint folder name

   AGENTS.md requires the primary service name to exactly match the blueprint folder name. The folder is trilium-next but the service is trilium_next (underscore instead of hyphen). These are treated as distinct identifiers.

   Context Used: Rule from dashboard - AGENTS.md (source)

5. General comment

   Absolute host paths in bind mounts are forbidden

   AGENTS.md explicitly prohibits absolute host paths in volume bind mounts. Three bind mounts here violate this rule:

   • ${TRILIUM_DATA_DIR:-~/trilium-data} — uses a ~-relative home directory path, which is an absolute path on the host
   • /etc/timezone:/etc/timezone:ro — absolute host path
   • /etc/localtime:/etc/localtime:ro — absolute host path

   For trilium-data, use a named volume instead. For timezone/locale, these are host-specific paths that are not portable in a Dokploy context and should be removed; the container image handles its own timezone.

   Context Used: Rule from dashboard - AGENTS.md (source)

6. General comment

   Docker images must be pinned to specific versions, not user-supplied variables

   Both ${PGDOG_IMAGE} and ${POSTGRES_IMAGE} (line 18) are environment variable references used as image names. This means the actual image to be pulled is entirely determined at runtime by the user, making the template non-deterministic and impossible to validate. AGENTS.md requires images to be pinned to specific versions to prevent supply chain attacks and ensure consistent deployments.

   Hardcode the image references to specific, tested version tags (e.g., pgdogio/pgdog:0.1.6 and postgres:17-alpine) and update meta.json accordingly.

   Context Used: Rule from dashboard - AGENTS.md (source)

7. General comment

   Broken healthcheck: CMD-SHELL requires a single shell string, not multiple arguments

   CMD-SHELL runs a command via the shell and expects a single string as its argument. When passed as an array like ["CMD-SHELL", "pg_isready", "-U", "...", "-d", "..."], only pg_isready is passed as the shell command — the -U and -d flags are silently ignored, so the healthcheck will succeed regardless of the database state.

   Additionally, environment variable substitution does not occur in the exec-form array — ${VIKUNJA_DATABASE_USER} will be passed as a literal string rather than the resolved value.

   (Use $ to escape the `## 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 Summary

This is a large bulk update PR touching 72 files — adding ~20 new blueprints and updating ~15 existing ones with version bumps, dependency fixes, and structural improvements. While many individual changes are sound (convex ports→expose fix, budibase/appsmith/grafana version bumps, supabase CONTAINER_PREFIX fix), the sheer scale of changes introduces numerous violations of the project's AGENTS.md conventions that need to be resolved before merging.

Critical issues requiring fixes:

• ports directive used in 4 blueprints (ipfs, trilium-next, verdaccio, vikunja) — this is explicitly forbidden; use expose + [[config.domains]] instead. The vikunja case is a regression.
• container_name: wg-easy added to wg-easy/docker-compose.yml — explicitly forbidden.
• Service name mismatches: wuzapi-server (folder: wuzapi) and trilium_next (folder: trilium-next) — must match exactly.
• Absolute host bind mounts in trilium-next (~/trilium-data, /etc/timezone, /etc/localtime) — forbidden per AGENTS.md.
• Version mismatches: mediafetch image uses latest but meta.json says 1.1.1; evolutionapi image changed to latest but meta.json still shows v2.1.2.
• Non-deterministic image references in postgres-pgdog (${PGDOG_IMAGE}, ${POSTGRES_IMAGE}) — images must be pinned to specific versions.
• Broken vikunja healthcheck: CMD-SHELL array form with env vars that won't be shell-substituted.
• Missing restart policy on verdaccio and openclaw main service.
• Missing version: "3.8" in openclaw, seaweedfs, strapi, and trilium-next.

Confidence Score: 1/5

• Not safe to merge — multiple new blueprints have critical convention violations and functional bugs that would break Dokploy deployments.
• There are 10+ distinct violations of the mandatory AGENTS.md conventions across multiple files: forbidden ports directives (4 files), forbidden container_name (1 file), service naming mismatches (2 files), absolute host bind mounts (1 file), version mismatches between meta.json and image tags (2 files), non-deterministic image references (1 file), a broken healthcheck (1 file), missing restart policies (2 files), and missing version: "3.8" declarations (4 files). Many of these would cause actual deployment failures in Dokploy.
• blueprints/ipfs/docker-compose.yml, blueprints/trilium-next/docker-compose.yml, blueprints/verdaccio/docker-compose.yml, blueprints/vikunja/docker-compose.yml, blueprints/wg-easy/docker-compose.yml, blueprints/wuzapi/docker-compose.yml, blueprints/mediafetch/docker-compose.yml, blueprints/evolutionapi/docker-compose.yml, blueprints/postgres-pgdog/docker-compose.yml, blueprints/openclaw/docker-compose.yml

so Docker performs the substitution at container runtime.)

8. General comment

   Missing version: "3.8" and restart policy; unpinned browser image

   Three issues in this file:

   1. Missing version: "3.8" — AGENTS.md requires all Dokploy blueprints to declare version: "3.8" at the top of the compose file. This also applies to blueprints/seaweedfs/docker-compose.yml, blueprints/strapi/docker-compose.yml, and blueprints/trilium-next/docker-compose.yml in this PR.
   2. openclaw service is missing a restart policy — add restart: unless-stopped or restart: always.
   3. coollabsio/openclaw-browser:latest — the browser service uses an unpinned latest tag. Pin it to a specific version to match the openclaw service version and update meta.json accordingly.

   Context Used: Rule from dashboard - AGENTS.md (source)

_{Last reviewed commit: d157cef}

Greptile also left 3 inline comments on this PR.

Context used:

• Rule from dashboard - AGENTS.md (source)

[cloudflare-workers-and-pages]

Deploying canary-templates with    Cloudflare Pages

Latest commit:	d157cef
Status:	⚡️  Build in progress...

View logs

[dosubot]

Related Documentation

Checked 7 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[greptile-apps]

Version mismatch between image tag and meta.json

AGENTS.md requires the version field in meta.json to exactly match the Docker image tag. meta.json lists "version": "1.1.1" for mediafetch, but the image here uses latest. Users will not be deploying the advertised 1.1.1 version.

Suggested change

	image: lukedunsmoto/mediafetch:latest
	image: lukedunsmoto/mediafetch:1.1.1

Context Used: Rule from dashboard - AGENTS.md (source)

[greptile-apps]

Version mismatch and unpinned latest tag

meta.json still has "version": "v2.1.2" for evolutionapi, but the image was changed to evoapicloud/evolution-api:latest. This violates the AGENTS.md requirement that the version field must match the image tag. Additionally, using latest means users will silently receive unverified future updates.

Please pin to a specific version tag and update meta.json to match.

Context Used: Rule from dashboard - AGENTS.md (source)

[greptile-apps]

Missing restart policy and forbidden ports directive

Two issues in this service:

1. There is no restart directive. AGENTS.md requires restart: unless-stopped or restart: always on every service.
2. ports: - 4873 is forbidden. Use expose: - 4873 and configure routing via [[config.domains]] in template.toml.

Suggested change

	verdaccio:
	image: verdaccio/verdaccio:6
	environment:
	- VERDACCIO_PORT=4873
	ports:
	- 4873
	verdaccio:
	image: verdaccio/verdaccio:6
	restart: unless-stopped
	environment:
	- VERDACCIO_PORT=4873
	expose:
	- 4873

Context Used: Rule from dashboard - AGENTS.md (source)