github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-06 10:37:26 -05:00
Code Issues 990 Packages Projects Releases Wiki Activity

[PR #790] [CLOSED] feat: add Velix API template #4263

New Issue
Closed
opened 2026-04-30 06:50:46 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 06:50:46 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/790
Author: @paulolinder
Created: 4/14/2026
Status: ❌ Closed

Base: canary ← Head: add-velix-api

📝 Commits (2)

📊 Changes

28 files changed (+1008 additions, -87 deletions)

View changed files

📝 blueprints/convex/docker-compose.yml (+8 -8)
📝 blueprints/evolutionapi/docker-compose.yml (+1 -1)
📝 blueprints/grafana/docker-compose.yml (+1 -1)
➕ blueprints/imgproxy/docker-compose.yml (+76 -0)
➕ blueprints/imgproxy/imgproxy.png (+0 -0)
➕ blueprints/imgproxy/template.toml (+56 -0)
➕ blueprints/mediafetch/docker-compose.yml (+18 -0)
➕ blueprints/mediafetch/mediafetch.svg (+1 -0)
➕ blueprints/mediafetch/template.toml (+15 -0)
📝 blueprints/nextcloud-aio/docker-compose.yml (+14 -12)
➖ blueprints/nextcloud-aio/nextcloud-aio.svg (+0 -1)
➕ blueprints/nextcloud-aio/nextcloud.png (+0 -0)
📝 blueprints/nextcloud-aio/template.toml (+166 -12)
📝 blueprints/notifuse/docker-compose.yml (+28 -30)
📝 blueprints/notifuse/template.toml (+2 -17)
➕ blueprints/tuwunel/docker-compose.yml (+18 -0)
➕ blueprints/tuwunel/template.toml (+15 -0)
➕ blueprints/tuwunel/tuwunel.svg (+4 -0)
➕ blueprints/unleash/docker-compose.yml (+49 -0)
➕ blueprints/unleash/template.toml (+17 -0)

...and 8 more files

📄 Description

Velix API

Self-hosted WhatsApp API built in Go with multi-instance support.

Services

  • velix-api: Go binary, port 8080, /data volume
  • postgres: PostgreSQL 16 for persistence
  • redis: Redis 7 for rate limiting

Features

  • Up to 200 WhatsApp instances
  • Full REST API (text, media, location, contacts, reactions, polls)
  • Real-time webhooks with HMAC-SHA256
  • Web admin panel with QR code pairing
  • Per-instance scoped API keys
  • n8n community node + AI Agent tool
  • Built-in Chatwoot integration

Docker Image

ghcr.io/paulolinder/velix-api:0.1.0

Links

Greptile Summary

This PR adds a new Velix API blueprint — a self-hosted WhatsApp gateway with PostgreSQL and Redis — following the standard Dokploy template structure. There is one blocking issue in template.toml that must be fixed before the template is functional.

  • Broken env syntax in template.toml: [config.env] is a TOML table (object), not the required array of strings. The generated variables will never be applied to the deployment, causing startup failures. The block must be rewritten as env = [...] inside [config], matching every other blueprint in the repo.

Confidence Score: 4/5

Not safe to merge — the broken template.toml env syntax will prevent the deployment from working at all.

One P1 issue (wrong TOML syntax for env vars) means the template is functionally broken out of the box; everything else is minor style. Score is 4 rather than lower because the fix is a one-line restructure with no architectural concerns.

blueprints/velix-api/template.toml requires the env syntax fix before this can be merged.

Reviews (1): Last reviewed commit: "feat: add Velix API template (WhatsApp A..." | Re-trigger Greptile

Greptile also left 3 inline comments on this PR.

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

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/790 **Author:** [@paulolinder](https://github.com/paulolinder) **Created:** 4/14/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-velix-api` --- ### 📝 Commits (2) - [`4902cbf`](https://github.com/Dokploy/templates/commit/4902cbf105d534a5c2d60c0351ec0e3609a338ed) New Version (#737) - [`5976110`](https://github.com/Dokploy/templates/commit/5976110f05dff8605a1d5d60e902f3b5c38a6f12) feat: add Velix API one-click template ### 📊 Changes **28 files changed** (+1008 additions, -87 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/convex/docker-compose.yml` (+8 -8) 📝 `blueprints/evolutionapi/docker-compose.yml` (+1 -1) 📝 `blueprints/grafana/docker-compose.yml` (+1 -1) ➕ `blueprints/imgproxy/docker-compose.yml` (+76 -0) ➕ `blueprints/imgproxy/imgproxy.png` (+0 -0) ➕ `blueprints/imgproxy/template.toml` (+56 -0) ➕ `blueprints/mediafetch/docker-compose.yml` (+18 -0) ➕ `blueprints/mediafetch/mediafetch.svg` (+1 -0) ➕ `blueprints/mediafetch/template.toml` (+15 -0) 📝 `blueprints/nextcloud-aio/docker-compose.yml` (+14 -12) ➖ `blueprints/nextcloud-aio/nextcloud-aio.svg` (+0 -1) ➕ `blueprints/nextcloud-aio/nextcloud.png` (+0 -0) 📝 `blueprints/nextcloud-aio/template.toml` (+166 -12) 📝 `blueprints/notifuse/docker-compose.yml` (+28 -30) 📝 `blueprints/notifuse/template.toml` (+2 -17) ➕ `blueprints/tuwunel/docker-compose.yml` (+18 -0) ➕ `blueprints/tuwunel/template.toml` (+15 -0) ➕ `blueprints/tuwunel/tuwunel.svg` (+4 -0) ➕ `blueprints/unleash/docker-compose.yml` (+49 -0) ➕ `blueprints/unleash/template.toml` (+17 -0) _...and 8 more files_ </details> ### 📄 Description ## Velix API Self-hosted WhatsApp API built in Go with multi-instance support. ### Services - **velix-api**: Go binary, port 8080, `/data` volume - **postgres**: PostgreSQL 16 for persistence - **redis**: Redis 7 for rate limiting ### Features - Up to 200 WhatsApp instances - Full REST API (text, media, location, contacts, reactions, polls) - Real-time webhooks with HMAC-SHA256 - Web admin panel with QR code pairing - Per-instance scoped API keys - n8n community node + AI Agent tool - Built-in Chatwoot integration ### Docker Image `ghcr.io/paulolinder/velix-api:0.1.0` ### Links - GitHub: https://github.com/paulolinder/velix-api - n8n node: https://www.npmjs.com/package/n8n-nodes-velix <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a new Velix API blueprint — a self-hosted WhatsApp gateway with PostgreSQL and Redis — following the standard Dokploy template structure. There is one blocking issue in `template.toml` that must be fixed before the template is functional. - **Broken env syntax in `template.toml`**: `[config.env]` is a TOML table (object), not the required array of strings. The generated variables will never be applied to the deployment, causing startup failures. The block must be rewritten as `env = [...]` inside `[config]`, matching every other blueprint in the repo. <h3>Confidence Score: 4/5</h3> Not safe to merge — the broken template.toml env syntax will prevent the deployment from working at all. One P1 issue (wrong TOML syntax for env vars) means the template is functionally broken out of the box; everything else is minor style. Score is 4 rather than lower because the fix is a one-line restructure with no architectural concerns. blueprints/velix-api/template.toml requires the env syntax fix before this can be merged. <sub>Reviews (1): Last reviewed commit: ["feat: add Velix API template (WhatsApp A..."](https://github.com/dokploy/templates/commit/c8a08fa12b779f9f41b4ec18b33469ce4f9ef54f) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28418797)</sub> > Greptile also left **3 inline comments** on this PR. <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **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-04-30 06:50:46 -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#4263
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?