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

1.0 KiB

systemprompt

Getting started

  1. Before the first deploy, set at least one AI provider key in Environment: ANTHROPIC_API_KEY, OPENAI_API_KEY, or GEMINI_API_KEY. The container will not boot without one.
  2. Enable HTTPS (Let's Encrypt) on the generated domain. The app validates EXTERNAL_URL and refuses plain http:// origins other than localhost — with HTTPS off it restart-loops with an "Invalid CORS origin" error.
  3. Deploy. The first boot runs database migrations and the publish pipeline; allow up to 5 minutes before the healthcheck goes green.
  4. Verify at https://<your-domain>/api/v1/health, then open the domain root for the admin UI.

Notes

  • POSTGRES_PASSWORD is auto-generated by the template; EXTERNAL_URL is derived from the domain you assign.
  • Web assets, storage, profile state, and Postgres data persist in the systemprompt_web, systemprompt_storage, systemprompt_profiles, and postgres_data volumes.
  • Docs: https://systemprompt.io/documentation/