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

[PR #794] feat(chatwoot): update blueprint to latest production layout #14220

New Issue
Open
opened 2026-06-17 06:23:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-17 06:23:51 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/794
Author: @juandelperal
Created: 4/16/2026
Status: 🔄 Open

Base: canary ← Head: canary

📝 Commits (3)

  • eff1206 Updated chatwoot blueprint
  • 79d9fec fix(chatwoot): align metadata and HTTPS defaults
  • 4fac6db chore(meta): dedupe and sort meta.json

📊 Changes

3 files changed (+49 additions, -52 deletions)

View changed files

📝 blueprints/chatwoot/docker-compose.yml (+40 -28)
📝 blueprints/chatwoot/template.toml (+8 -5)
📝 meta.json (+1 -19)

📄 Description

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)

🔄 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/794 **Author:** [@juandelperal](https://github.com/juandelperal) **Created:** 4/16/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `canary` --- ### 📝 Commits (3) - [`eff1206`](https://github.com/Dokploy/templates/commit/eff1206132f1a99958404fa9ac24a7af82da9d1c) Updated chatwoot blueprint - [`79d9fec`](https://github.com/Dokploy/templates/commit/79d9fec567e1c6c4cb378abdf14608849e1220fe) fix(chatwoot): align metadata and HTTPS defaults - [`4fac6db`](https://github.com/Dokploy/templates/commit/4fac6db5c3a309fb2ac417598841d3e15dbb0474) chore(meta): dedupe and sort meta.json ### 📊 Changes **3 files changed** (+49 additions, -52 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/chatwoot/docker-compose.yml` (+40 -28) 📝 `blueprints/chatwoot/template.toml` (+8 -5) 📝 `meta.json` (+1 -19) </details> ### 📄 Description ## 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 - [x] Validate YAML/TOML structure after edits - [x] Ensure `template.toml` domain service points to `chatwoot` service - [x] Generate Dokploy base64 import payload locally and verify it can be copied/imported - [x] Import this template in Dokploy and run a full deployment smoke test Made with [Cursor](https://cursor.com) <!-- greptile_comment --> <h3>Greptile Summary</h3> 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. <h3>Confidence Score: 4/5</h3> 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. <sub>Reviews (1): Last reviewed commit: ["Updated chatwoot blueprint"](https://github.com/dokploy/templates/commit/eff1206132f1a99958404fa9ac24a7af82da9d1c) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28683724)</sub> > Greptile also left **2 inline comments** on this PR. **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-17 06:23:51 -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#14220
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?