feat: Update Glitchtip to version 6.1.0

[andrew-tinekov]

What is this PR about?

Update Glitchtip to version 6.1.0

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.

Screenshots or Videos

Greptile Summary

This PR updates the Glitchtip template from v4.0 to 6.1.0, replacing Redis with Valkey, upgrading PostgreSQL from 16 to 18, switching from ports to expose (correct per conventions), and updating worker/migrate startup commands to match the new release's script layout.

Key changes:

• glitchtip/glitchtip:v4.0 → glitchtip/glitchtip:6.1.0 across all three services
• redis replaced with valkey/valkey:9; VALKEY_URL env var added
• GLITCHTIP_DOMAIN now properly constructed with https:// prefix and configurable DEFAULT_FROM_EMAIL via ${email} helper
• Worker command updated to ./bin/run-worker.sh; migrate command updated to ./bin/run-migrate.sh
• version: "3.8" correctly added to the compose file
• ports correctly replaced with expose

Issues found:

• The PostgreSQL volume mount was changed from pg-data:/var/lib/postgresql/data to pg-data:/var/lib/postgresql. While this works for fresh deployments, it would cause any existing deployment being upgraded to lose access to its data, since PostgreSQL's PGDATA still resolves to /var/lib/postgresql/data (a subdirectory of the new mount) rather than the root of the previously populated volume.
• meta.json lists the version as v6.1.0 while the Docker image tag is 6.1.0 — these should match exactly per the project's AGENTS.md guide.

Confidence Score: 3/5

• Safe for new deployments, but the postgres volume path change is a data-loss risk for users upgrading from the previous template version.
• The overall update is well-structured and the v6.1.0 changes (Valkey, new script paths, https domain, expose vs ports) are all correct. However, the postgres volume mount path regression (/var/lib/postgresql vs /var/lib/postgresql/data) could silently wipe existing data for upgrading users, which is a meaningful reliability concern. The meta.json version prefix inconsistency is minor but straightforward to fix.
• blueprints/glitchtip/docker-compose.yml — specifically the postgres volume mount path on line 23.

_{Reviews (1): Last reviewed commit: "feat(glitchtip): update to version 6.1.0" | Re-trigger Greptile}

Greptile also left 2 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)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	4049760

[andrew-tinekov]

About Validate and Process Meta.json – not related to my changes:

[2026-03-23T19:35:23.228Z] 🔧 Starting meta.json processing...
[2026-03-23T19:35:23.230Z] 🔧 Found 389 total entries
[2026-03-23T19:35:23.231Z] ⚠️ Duplicate ID found: "strapi" (Strapi)
[2026-03-23T19:35:23.234Z] ✅ Processing completed in 6ms
[2026-03-23T19:35:23.234Z] 🔧 Statistics:
[2026-03-23T19:35:23.234Z] 🔧   • Original entries: 389
[2026-03-23T19:35:23.234Z] 🔧   • Duplicates removed: 1
[2026-03-23T19:35:23.234Z] 🔧   • Final entries: 388
[2026-03-23T19:35:23.234Z] 🔧   • Schema violations: 0
[2026-03-23T19:35:23.234Z] ⚠️ Removed duplicates:
[2026-03-23T19:35:23.234Z] ⚠️   • "strapi" (Strapi)