Skip to content

feat(chatwoot): update blueprint to latest production layout#794

Open
juandelperal wants to merge 3 commits intoDokploy:canaryfrom
juandelperal:canary
Open

feat(chatwoot): update blueprint to latest production layout#794
juandelperal wants to merge 3 commits intoDokploy:canaryfrom
juandelperal:canary

Conversation

@juandelperal
Copy link
Copy Markdown

@juandelperal juandelperal commented Apr 16, 2026

Summary

  • update Chatwoot blueprint to align with the latest upstream docker production structure while keeping Dokploy conventions
  • pin Chatwoot image to v4.12.1, update Postgres to pg16, and keep persistent volumes/restart policy
  • fix runtime issues by removing missing init-vector.sql mount and wiring Redis auth/env vars consistently in docker-compose.yml and template.toml

Test plan

  • Validate YAML/TOML structure after edits
  • Ensure template.toml domain service points to chatwoot service
  • Generate Dokploy base64 import payload locally and verify it can be copied/imported
  • Import this template in Dokploy and run a full deployment smoke test

Made with Cursor

Greptile Summary

This PR updates the Chatwoot blueprint to align with the upstream v4.12.1 production Docker layout: the Compose version is bumped to 3.8, services are renamed to match Dokploy conventions (chatwoot as main service), the broken init-vector.sql bind-mount is removed, and Redis authentication is properly wired via a generated redis_password variable.

  • meta.json version mismatch: The image is pinned to v4.12.1 but meta.json still reports v3.14.1 — the version field must be updated to match per project conventions.
  • FRONTEND_URL uses http://: This will produce incorrect links (OAuth callbacks, asset URLs) on any HTTPS deployment; defaulting to https:// is safer.

Confidence Score: 4/5

Safe to merge after updating meta.json version to v4.12.1; the http:// frontend URL is worth fixing for HTTPS setups but isn't blocking.

One P1 remains: meta.json version is out of sync with the pinned Docker image tag, which violates the documented project requirement. All other changes are correct improvements over the previous blueprint.

meta.json (not in the diff) must be updated to set version v4.12.1 for the chatwoot entry.

Reviews (1): Last reviewed commit: "Updated chatwoot blueprint" | Re-trigger Greptile

Greptile also left 2 inline comments on this PR.

Context used:

  • Context used - AGENTS.md (source)

@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Apr 16, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 16, 2026

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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

Comment thread blueprints/chatwoot/docker-compose.yml
Comment thread blueprints/chatwoot/template.toml Outdated
Update Chatwoot metadata to match the pinned image version and default the template URL/SSL settings for Dokploy TLS deployments.

Made-with: Cursor
Remove duplicate strapi entry so processed meta matches CI expectations.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant