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

36 lines
1.9 KiB
YAML

services:
minio:
# MinIO Inc. stopped publishing Docker images and pre-built binaries in October 2025
# (https://github.com/minio/minio/issues/21647) and archived the minio/minio repository
# in February 2026. The official minio/minio image is frozen at RELEASE.2025-09-07T16-13-09Z
# and no longer receives security fixes (e.g. the fix for CVE-2025-62506 was never published
# as an image). This template uses pgsty/minio, the actively maintained community fork
# (https://github.com/pgsty/minio, AGPLv3). It is a drop-in replacement: same environment
# variables, same `server` command, same /data on-disk format (existing minio-data volumes
# keep working), and it restores the full web console that upstream removed.
image: pgsty/minio:RELEASE.2026-06-18T00-00-00Z
restart: unless-stopped
volumes:
# by default, the MinIO container will use a volume named minio-data
# to store its data. This volume is created automatically by Docker.
# If you want to use a local directory instead, uncomment the line below
# and specify the path to your local directory.
# (be warned that ../files is pointing to a subdirectory of /etc/dokploy/compose in dokploy)
# - ../files/minio-data:/data
# if you uncommented the line above, comment the line below and the volumes section at the end
- minio-data:/data
environment:
- MINIO_ROOT_USER=${MINIO_ROOT_USER}
- MINIO_ROOT_PASSWORD=${MINIO_ROOT_PASSWORD}
- MINIO_BROWSER_REDIRECT_URL=${MINIO_BROWSER_REDIRECT_URL}
command: server /data --console-address ":9001"
expose:
# port 9000 serves the S3 API (routed through the api domain defined in template.toml)
# port 9001 serves the web console (routed through the main domain)
- 9000
- 9001
# comment the line below if you specified a local directory in the volumes section of the minio service
volumes:
minio-data: