mirror of
https://github.com/hanzoai/templates-blueprints.git
synced 2026-10-30 14:55:00 +00:00
zeekay
cf4d0b027e
Aggregates five OSS one-click/self-hosting catalogs into the Dokploy blueprint
shape the Hanzo PaaS consumes (meta.json array + blueprints/<id>/{template.toml,
docker-compose.yml,meta.json,logo}):
Dokploy 500 (MIT, verbatim) · Coolify 174 (Apache-2.0) · CapRover 161
(Apache-2.0) · CasaOS 85 (Apache-2.0) · Runtipi 110 (GPL-3.0)
Deduped by app identity; each source + app keeps its upstream license
(ATTRIBUTION.md). Deterministic aggregators + a hard validator (every
template.toml parses with the platform's toml lib, every compose parses as YAML,
meta.json is the expected array, and an over-HTTP fetch probe exercises all
1030) — 0 hard failures. Served natively by hanzoai/static on DOKS (no CDN/Pages/
Vercel); CI builds on the hanzo-build-linux-amd64 arc pool; operator App CR in
crs/ serves it at templates.hanzo.ai.
1.5 KiB
1.5 KiB
n8n Queue Mode
This template runs n8n in queue mode:
- n8n (main): serves the editor UI and receives webhooks/triggers, then publishes executions to the queue.
- n8n-worker (x2 by default): pulls executions from the Redis (Bull) queue and runs them.
- redis: the message broker for the queue (password protected).
- postgres: stores workflows, credentials and execution data.
All n8n containers share the same N8N_ENCRYPTION_KEY (generated automatically), which is required for workers to decrypt credentials.
Scaling workers
Worker replicas are controlled by the N8N_WORKER_REPLICAS environment variable (default 2):
- Open the compose service in Dokploy and go to the Environment tab.
- Change
N8N_WORKER_REPLICASto the number of workers you want. - Redeploy. Docker Compose will scale the
n8n-workerservice to the requested number of replicas.
Each worker runs up to 10 concurrent executions by default. You can tune this by adding N8N_CONCURRENCY_PRODUCTION_LIMIT to the worker environment.
Optional: dedicated webhook processors
For very high webhook volumes, n8n supports dedicated webhook processor instances (command: webhook). To use them, add another service to the compose file with the same environment as n8n-worker but with command: webhook, and route the /webhook/ path of your domain to it. See the n8n queue mode docs for details.