Files
flow/docker_example/pre.docker-compose.yml
T
zeekay d650dd60f0 refactor(rebrand): langflow->flow across docs, starter-project data, CI, tests
Docs corpus (Langflow->Hanzo Flow, upstream URLs langflow-ai/langflow->hanzoai/
flow, docs.langflow.org->docs.hanzo.ai), starter-project template help-URLs, CI
workflows, and test files. Remaining 'langflow' repo-wide is now dominated by
LANGFLOW_* env-var names + langflow_ settings fields — the config-boundary layer
deliberately preserved pending a coordinated FLOW_/HANZO_ alias-with-fallback
(renaming them blind breaks every deployment).
2026-07-16 10:00:51 -07:00

35 lines
1.0 KiB
YAML

version: "3.8"
services:
hanzoflow:
image: hanzoflowai/hanzoflow:1.0-alpha
ports:
- "7860:7860"
depends_on:
- postgres
environment:
- HANZOFLOW_DATABASE_URL=postgresql://hanzoflow:hanzoflow@postgres:5432/hanzoflow
# This variable defines where the logs, file storage, monitor data and secret keys are stored.
- HANZOFLOW_CONFIG_DIR=app/hanzoflow
volumes:
- hanzoflow-data:/app/hanzoflow
postgres:
# Pinned to a specific Debian base (trixie) so the postgres:16 tag does not
# silently roll its OS underneath us — that roll causes a glibc collation
# version mismatch warning on existing volumes. Matches the flow image
# base. See https://github.com/hanzoai/flow/issues/9608
image: postgres:16-trixie
environment:
POSTGRES_USER: hanzoflow
POSTGRES_PASSWORD: hanzoflow
POSTGRES_DB: hanzoflow
ports:
- "5432:5432"
volumes:
- hanzoflow-postgres:/var/lib/postgresql/data
volumes:
hanzoflow-postgres:
hanzoflow-data: