mirror of
https://github.com/hanzo-apps/templates.git
synced 2026-10-30 14:48:30 +00:00
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.
75 lines
2.2 KiB
YAML
75 lines
2.2 KiB
YAML
# This is an UNOFFICIAL production docker image build for Superset:
|
|
# - https://github.com/amancevice/docker-superset
|
|
#
|
|
#
|
|
# ## SETUP INSTRUCTIONS
|
|
#
|
|
# After deploying this image, you will need to run one of the two
|
|
# commands below in a terminal within the superset container:
|
|
# $ superset-demo # Initialise database + load demo charts/datasets
|
|
# $ superset-init # Initialise database only
|
|
#
|
|
# You will be prompted to enter the credentials for the admin user.
|
|
#
|
|
#
|
|
# ## NETWORK INSTRUCTIONS
|
|
#
|
|
# If you want to connect superset with other internal databases managed by
|
|
# Dokploy using internal hostnames, you will need to connect the `superset`
|
|
# container to those networks.
|
|
#
|
|
|
|
services:
|
|
superset:
|
|
image: amancevice/superset:6.0.0
|
|
restart: unless-stopped
|
|
#networks:
|
|
# - dokploy-network
|
|
depends_on:
|
|
- superset_postgres
|
|
- superset_redis
|
|
volumes:
|
|
# This superset_config.py can be edited in Dokploy's UI Advanced -> Volume Mount
|
|
- ../files/superset/superset_config.py:/etc/superset/superset_config.py
|
|
environment:
|
|
SECRET_KEY: ${SECRET_KEY}
|
|
MAPBOX_API_KEY: ${MAPBOX_API_KEY}
|
|
POSTGRES_USER: ${POSTGRES_USER}
|
|
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
|
|
POSTGRES_DB: ${POSTGRES_DB}
|
|
REDIS_PASSWORD: ${REDIS_PASSWORD}
|
|
# Ensure the hosts matches your service names below.
|
|
POSTGRES_HOST: superset_postgres
|
|
REDIS_HOST: superset_redis
|
|
|
|
superset_postgres:
|
|
image: postgres:18
|
|
restart: unless-stopped
|
|
environment:
|
|
POSTGRES_USER: ${POSTGRES_USER}
|
|
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
|
|
POSTGRES_DB: ${POSTGRES_DB}
|
|
volumes:
|
|
- superset_postgres_data:/var/lib/postgresql
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
|
|
interval: 30s
|
|
timeout: 10s
|
|
retries: 3
|
|
|
|
superset_redis:
|
|
image: redis:8
|
|
restart: unless-stopped
|
|
volumes:
|
|
- superset_redis_data:/data
|
|
command: redis-server --requirepass ${REDIS_PASSWORD}
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "redis-cli -a $${REDIS_PASSWORD} ping"]
|
|
interval: 30s
|
|
timeout: 10s
|
|
retries: 3
|
|
|
|
volumes:
|
|
superset_postgres_data:
|
|
superset_redis_data:
|