New templates

[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

Large PR adding 11 new templates (cloudflare-ddns, ipfs, openclaw, postgres-pgdog, pulse, seaweedfs, strapi, trilium-next, wuzapi, cloudflare-ddns, habitica overhaul) and updating ~12 existing templates (alist, appsmith, budibase, cloudflared, habitica, invoiceshelf, nextcloud-aio, supabase, superset, trmnl-byos-laravel, uptime-kuma, vikunja, wg-easy). Also adds PR guidelines to CONTRIBUTING.md and volume bind mount guidance to AGENTS.md.

• Critical: Postgres volume path regression — Three templates (superset, strapi, postgres-pgdog) mount the Postgres data volume to /var/lib/postgresql instead of the correct /var/lib/postgresql/data. The superset template previously had the correct path and was changed in this PR. This will cause data persistence failures.
• Critical: Openclaw browser port mismatch — BROWSER_CDP_URL references port 9223 but the browser service listens on 9222, preventing the openclaw service from connecting.
• Critical: Vikunja healthcheck syntax — The DB healthcheck uses CMD-SHELL with multiple array arguments instead of a single command string. Docker will only pass the first argument to the shell, causing the healthcheck to always fail.
• Multiple meta.json version mismatches — Six templates have version discrepancies between meta.json and their docker-compose.yml image tags: cloudflare-ddns, openclaw, pulse, seaweedfs, trilium-next, and wuzapi.
• Trilium-next issues — Data directory mismatch between template.toml (TRILIUM_DATA_DIR=/root) and the volume mount path, host path bind mounts instead of named volumes, and a typo (mount instead of mounts) in template.toml.
• wg-easy adds container_name — Violates Dokploy template conventions per AGENTS.md.
• Positive changes — Budibase removes the watchtower service (good cleanup), several templates get version bumps with pinned images, and the Habitica template gets proper MongoDB authentication with replica set support.

Confidence Score: 2/5

• This PR has several runtime-breaking issues that need to be fixed before merging.
• Score of 2 reflects multiple confirmed bugs: wrong Postgres volume paths in 3 templates (will break data persistence), a port mismatch in openclaw (browser connection will fail), broken healthcheck syntax in vikunja, and 6 version mismatches between meta.json and docker-compose files. While much of the PR is solid (version upgrades, new templates with good structure), these issues will cause runtime failures for users deploying these templates.
• Pay close attention to: blueprints/superset/docker-compose.yml, blueprints/strapi/docker-compose.yml, blueprints/postgres-pgdog/docker-compose.yml (Postgres volume paths), blueprints/openclaw/docker-compose.yml (port mismatch), blueprints/vikunja/docker-compose.yml (healthcheck syntax), blueprints/trilium-next/ (multiple issues), and meta.json (version mismatches).

_{Last reviewed commit: 38e417b}

Context used:

• Context from dashboard - AGENTS.md (source)

[greptile-apps]

_{49 files reviewed, 14 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Browser CDP port mismatch
The BROWSER_CDP_URL is set to port 9223, but the browser service configures Chrome's remote debugging port as 9222 (line 73: CHROME_CLI=--remote-debugging-port=9222), and the browser healthcheck also checks port 9222 (line 78). This mismatch means openclaw will fail to connect to the browser.

Suggested change

	- BROWSER_CDP_URL=http://browser:9223
	- BROWSER_CDP_URL=http://browser:9222

[greptile-apps]

Invalid healthcheck syntax for CMD-SHELL
When using CMD-SHELL, the entire command must be passed as a single string (the shell receives it as one argument to /bin/sh -c). Splitting into multiple array elements after CMD-SHELL will cause the healthcheck to fail because Docker only passes the second element as the shell command, ignoring the rest. Other Postgres healthchecks in this repo (e.g., strapi, superset) use the correct format.

Suggested change

	test: ["CMD-SHELL", "pg_isready", "-U", "${VIKUNJA_DATABASE_USER}", "-d", "${VIKUNJA_DATABASE_DATABASE}"]
	test: ["CMD-SHELL", "pg_isready -U ${VIKUNJA_DATABASE_USER} -d ${VIKUNJA_DATABASE_DATABASE}"]

[greptile-apps]

Incorrect Postgres data volume path
The volume mount changed from /var/lib/postgresql/data (the standard PostgreSQL data directory) to /var/lib/postgresql. The official Postgres Docker image stores data in /var/lib/postgresql/data, so mounting a volume to the parent directory (/var/lib/postgresql) means the actual data subdirectory won't be persisted correctly across container restarts, and may also cause conflicts with PostgreSQL initialization scripts.

Suggested change

	- superset_postgres_data:/var/lib/postgresql
	- superset_postgres_data:/var/lib/postgresql/data

[greptile-apps]

Incorrect Postgres data volume path
Same issue as in superset: the volume should mount to /var/lib/postgresql/data, not /var/lib/postgresql. The official Postgres Docker image stores its data in the data subdirectory, and mounting to the parent directory will cause data persistence issues.

Suggested change

	- strapi_postgres_data:/var/lib/postgresql
	- strapi_postgres_data:/var/lib/postgresql/data

[greptile-apps]

Incorrect Postgres data volume path
Same issue as in the other templates: the volume should mount to /var/lib/postgresql/data, not /var/lib/postgresql. The official Postgres Docker image uses the data subdirectory for its data files.

Suggested change

	- postgres-data:/var/lib/postgresql
	- postgres-data:/var/lib/postgresql/data

[greptile-apps]

Version mismatch with docker-compose image tag
The meta.json version is 2026.1.29, but the docker-compose.yml uses coollabsio/openclaw:2026.2.6. Per AGENTS.md, the version in meta.json must match the Docker image tag. Update to 2026.2.6.

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

[greptile-apps]

Version mismatch with docker-compose image tag
The meta.json version for Pulse is latest, but docker-compose.yml pins the image to rcourtman/pulse:5.1. Per AGENTS.md, the version must match the Docker image tag. Update to 5.1.

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

[greptile-apps]

Version mismatch with docker-compose image tag
The meta.json version for SeaweedFS is latest, but docker-compose.yml pins the image to chrislusf/seaweedfs:4.02. Per AGENTS.md, the version must match the Docker image tag. Update to 4.02.

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

[greptile-apps]

Version mismatch with docker-compose image tag
The meta.json version for TriliumNext is latest, but docker-compose.yml pins the image to triliumnext/trilium:v0.101.3. Per AGENTS.md, the version must match. Update to v0.101.3.

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

[greptile-apps]

Version mismatch with docker-compose image tag
The meta.json version for WuzAPI is v1.0.0, but docker-compose.yml uses the SHA-based tag asternic/wuzapi:sha-30c1805. These don't match — either pin the image to a semantic version tag or update meta.json to reflect the SHA tag.

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