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.5 KiB

SpacetimeDB

SpacetimeDB is a database and server runtime in one: your clients connect directly to the database and your application logic runs inside it as WebAssembly modules. There is no web UI — the domain assigned to this service exposes the SpacetimeDB HTTP/WebSocket API (so opening / in a browser returns a plain 404; that is expected).

Verify the server is running

curl -i https://your-domain.com/v1/ping

A 200 OK response means the server is up.

Connect with the SpacetimeDB CLI

  1. Install the CLI on your local machine:

    curl -sSf https://install.spacetimedb.com | sh
    
  2. Register your Dokploy instance as a server and make it the default:

    spacetime server add --url https://your-domain.com dokploy --default
    
  3. Log in (or create an anonymous local identity) and publish a module:

    spacetime login
    spacetime publish --server dokploy my-database
    
  4. Check connectivity at any time:

    spacetime server ping dokploy
    

From your game or app, connect with any SpacetimeDB client SDK (Rust, C#, TypeScript) using https://your-domain.com as the host URI. See the getting started guide for a full walkthrough.

Notes

  • All server state (databases, logs and the JWT signing keys used for identities) is persisted in the spacetimedb-data volume, so identities survive restarts and upgrades.
  • Client connections use WebSockets over the same domain; no extra configuration is needed.