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
Instructions
Synapse is deployed with public registration disabled, so you need to create the first user (your admin account) from the command line.
Create the first user
Open a terminal on the server running Dokploy (or use the container terminal in
the Dokploy UI) and run the following inside the synapse service container:
docker exec -it $(docker ps -qf "name=synapse" | head -n 1) \
register_new_matrix_user http://localhost:8008 -c /config/homeserver.yaml
The tool prompts for a username and password, and asks whether the user should
be an admin. It authenticates against the server using the
registration_shared_secret that was generated for this deployment (stored in
the mounted homeserver.yaml), so no registration needs to be enabled.
Log in
Point any Matrix client (for example Element Web at https://app.element.io) at
your homeserver URL https://your-domain and log in with the user you just
created. You can verify the server is up with:
curl https://your-domain/_matrix/client/versions
Notes
- Data (signing keys, media uploads) is stored in the
synapse-datavolume and the database in thepostgres-datavolume. - Federation with other Matrix servers works through
.well-knowndelegation over HTTPS (port 443). The dedicated federation port 8448 is not exposed. - To allow open registration instead, edit
enable_registrationin the mountedhomeserver.yaml(see Synapse docs for the required spam-check options such as CAPTCHA or email verification).