feat: add Velix API one-click template

[paulolinder]

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)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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

[greptile-apps]

Unconventional integer literal for port

8_080 is valid TOML 1.0 (underscores are allowed as visual separators in integer literals), but it's non-standard compared to every other template in this repository, which all use 8080. If any intermediate TOML parser used by Dokploy isn't fully 1.0-compliant with this feature, the domain binding would silently fail to resolve.

Suggested change

	serviceName = "velix-api"
	port = 8080

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!