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.2 KiB
Instructions
First setup
- The first boot runs the database migrations, so it can take 2-4 minutes before the application responds.
- Open your domain: you will be redirected to
/install, where you create the admin (workspace owner) account. - After signing in, go to Settings -> Model Provider and install a model provider plugin (OpenAI, Anthropic, Ollama, etc.) from the marketplace, then configure your API keys.
Notes
-
HTTPS is required for the console login: Dify issues
__Host-/Securesession cookies, so make sure the domain has a certificate (e.g. Let's Encrypt in the domain settings). Over plain HTTP the browser will drop the session cookies and login will not persist. -
The vector store is pgvector, running inside the bundled PostgreSQL instance (no separate Weaviate/Qdrant container needed).
-
All routing (
/console/api,/api,/v1,/files,/e/, ...) is handled by the bundled internal nginx gateway, mirroring the upstream deployment, so the Dify service API is available athttps://<your-domain>/v1. -
Code execution runs in the isolated
sandboxservice, and user-triggered outbound HTTP requests go through thessrf_proxy(squid) service, like in the official deployment.