[PR #793] feat: add Velix API one-click template #1317

New Issue

GiteaMirror · 2026-04-16T11:34:06-05:00

GiteaMirror commented

2026-04-16 11:34:06 -05:00

📋 Pull Request Information

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

Base: main ← Head: add-velix-api

📝 Commits (2)

5976110 feat: add Velix API one-click template
35b953e fix: use standard port integer literal

📊 Changes

4 files changed (+93 additions, -0 deletions)

View changed files

➕ blueprints/velix-api/docker-compose.yml (+43 -0)
➕ blueprints/velix-api/template.toml (+16 -0)
➕ blueprints/velix-api/velix-api.svg (+16 -0)
📝 meta.json (+18 -0)

📄 Description

Summary

Added Velix API as a new one-click blueprint. Velix is a self-hosted WhatsApp API built in Go with multi-instance support, webhooks, n8n node, and Chatwoot integration.

Services included:

velix-api (Go, port 8080)
PostgreSQL 16
Redis 7

Security: Registration is disabled by default (REGISTRATION_ENABLED=false).

Docker image: ghcr.io/paulolinder/velix-api:0.1.0

Preview

Admin panel accessible at the configured domain on port 8080 for QR code pairing and WhatsApp instance management.

Greptile Summary

This PR adds Velix API — a self-hosted WhatsApp API — as a new one-click blueprint with a Go service, PostgreSQL 16, and Redis 7. The template follows all Dokploy conventions correctly: version 3.8, no ports/container_name/networks, restart: always, named volumes, and secrets properly randomized via template helpers. The only minor issue is port = 8_080 in template.toml using TOML's underscore integer literal instead of the standard 8080 used by all other templates in this repository.

Confidence Score: 5/5

Safe to merge — all conventions are followed and the single finding is a non-blocking style suggestion.

All changed files conform to AGENTS.md requirements: correct compose version, no forbidden fields, pinned image versions, secrets randomized, meta.json fields complete and version-matched. The only finding is a P2 style issue (underscore integer notation in template.toml) that doesn't affect runtime behavior given TOML 1.0 compliance.

blueprints/velix-api/template.toml — minor port notation style issue on line 14.

_{Reviews (1): Last reviewed commit: "feat: add Velix API one-click template" | Re-trigger Greptile}

Greptile also left 1 inline comment 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/793 **Author:** [@paulolinder](https://github.com/paulolinder) **Created:** 4/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-velix-api` --- ### 📝 Commits (2) - [`5976110`](https://github.com/Dokploy/templates/commit/5976110f05dff8605a1d5d60e902f3b5c38a6f12) feat: add Velix API one-click template - [`35b953e`](https://github.com/Dokploy/templates/commit/35b953e40a7e935a72dfa40c8add587d2bd0a516) fix: use standard port integer literal ### 📊 Changes **4 files changed** (+93 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/velix-api/docker-compose.yml` (+43 -0) ➕ `blueprints/velix-api/template.toml` (+16 -0) ➕ `blueprints/velix-api/velix-api.svg` (+16 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description ## Summary Added Velix API as a new one-click blueprint. Velix is a self-hosted WhatsApp API built in Go with multi-instance support, webhooks, n8n node, and Chatwoot integration. **Services included:** - velix-api (Go, port 8080) - PostgreSQL 16 - Redis 7 **Security:** Registration is disabled by default (`REGISTRATION_ENABLED=false`). **Docker image:** `ghcr.io/paulolinder/velix-api:0.1.0` ## Preview Admin panel accessible at the configured domain on port 8080 for QR code pairing and WhatsApp instance management.  <h3>Greptile Summary</h3> This PR adds Velix API — a self-hosted WhatsApp API — as a new one-click blueprint with a Go service, PostgreSQL 16, and Redis 7. The template follows all Dokploy conventions correctly: version 3.8, no `ports`/`container_name`/`networks`, `restart: always`, named volumes, and secrets properly randomized via template helpers. The only minor issue is `port = 8_080` in `template.toml` using TOML's underscore integer literal instead of the standard `8080` used by all other templates in this repository. <h3>Confidence Score: 5/5</h3> Safe to merge — all conventions are followed and the single finding is a non-blocking style suggestion. All changed files conform to AGENTS.md requirements: correct compose version, no forbidden fields, pinned image versions, secrets randomized, meta.json fields complete and version-matched. The only finding is a P2 style issue (underscore integer notation in template.toml) that doesn't affect runtime behavior given TOML 1.0 compliance. blueprints/velix-api/template.toml — minor port notation style issue on line 14. <sub>Reviews (1): Last reviewed commit: ["feat: add Velix API one-click template"](https://github.com/dokploy/templates/commit/5976110f05dff8605a1d5d60e902f3b5c38a6f12) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28587964)</sub> > Greptile also left **1 inline comment** on this PR. **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <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-16 11:34:06 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#1317