Files
zeekay cf4d0b027e templates.hanzo.ai: 1030-blueprint one-click deploy catalog
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.
2026-07-24 01:46:23 -07:00

44 lines
1.4 KiB
TOML

[variables]
main_domain = "${domain}"
postgres_password = "${password:32}"
load_demo = "false"
java_opts = "-Xms512m -Xmx2048m"
[[config.domains]]
serviceName = "thingsboard"
port = 8080
host = "${main_domain}"
path = "/"
[[config.mounts]]
filePath = "README.md"
content = """# ThingsBoard
This template deploys ThingsBoard Community Edition with PostgreSQL using the official `thingsboard/tb-node` Docker image.
## First start
The `thingsboard-init` service initializes the database once before the main service starts. By default it performs a clean install. Set `load_demo` to `true` before deploying if you want ThingsBoard's sample tenant, dashboards, and demo devices.
## Login
Open `https://${main_domain}` and sign in with the default system administrator account:
- Email: `[email protected]`
- Password: `sysadmin`
Change the default password before exposing the instance to production users.
## Device connectivity
The web UI and HTTP device API are available through the configured domain. MQTT, CoAP, and additional transport ports are not publicly exposed by this template; expose them separately in Dokploy if your deployment requires direct device connections over those protocols.
"""
[config.env]
POSTGRES_DB = "thingsboard"
POSTGRES_USER = "postgres"
POSTGRES_PASSWORD = "${postgres_password}"
LOAD_DEMO = "${load_demo}"
JAVA_OPTS = "${java_opts}"
SECURITY_CORS_ALLOWED_ORIGINS = "http://${main_domain},https://${main_domain}"