为什么:v2.0 代码侧已 ready,但 docker compose up 起来会立刻 panic
(表不存在),且密码硬编码、Binance 直连超时、无 healthcheck。
修复:
1. migrate init container(migrate/migrate:v4.18.1)
- depends_on postgres service_healthy 后执行
- 跑完 up 退出;app depends_on migrate service_completed_successfully
- 表不存在的 race 彻底消除
2. postgres healthcheck(pg_isready)
- interval 5s、retries 10、start_period 10s
- app 不再在 init 期连接失败
3. .env + .env.example(守卫 G9)
- 密码、端口、Binance URL 全部从环境变量读
- POSTGRES_PASSWORD 未设置时 docker-compose 直接报错退出(${VAR:?...} 语法)
- .env 已在 .gitignore,.env.example 留作模板
4. HTTP_PROXY/HTTPS_PROXY/NO_PROXY 透传
- 国内直连 fapi.binance.com 不稳(AGENTS.md §7.5)
- NO_PROXY 默认包含 postgres 容器名,避免本地代理误走
附加:config 卷只读挂载(防容器内意外写入);ports 端口可由
.env 覆盖;postgres 容器名走 docker DNS(替换之前硬编码的
crypto-hermes-postgres)。
验证:python yaml lint 通过;依赖链 postgres healthy →
migrate completed → app start 已确认。docker 在本机不可用,
线上验证留给 commit 9 之后的人工 smoke。
64 lines
2.1 KiB
YAML
64 lines
2.1 KiB
YAML
services:
|
||
postgres:
|
||
image: timescale/timescaledb:latest-pg16
|
||
container_name: crypto-hermes-postgres
|
||
environment:
|
||
POSTGRES_USER: ${POSTGRES_USER:-postgres}
|
||
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:?POSTGRES_PASSWORD must be set, see .env.example}
|
||
POSTGRES_DB: ${POSTGRES_DB:-hermes_market}
|
||
ports:
|
||
- "${POSTGRES_PORT:-5432}:5432"
|
||
volumes:
|
||
- hermes_pg_data:/var/lib/postgresql/data
|
||
healthcheck:
|
||
# 用 pg_isready 探测,避免 init 期 race
|
||
test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-postgres} -d ${POSTGRES_DB:-hermes_market}"]
|
||
interval: 5s
|
||
timeout: 3s
|
||
retries: 10
|
||
start_period: 10s
|
||
|
||
# init container:跑完 migration 立即退出。
|
||
# 由 app 依赖它 service_completed_successfully,保证表存在再启动 app。
|
||
migrate:
|
||
image: migrate/migrate:v4.18.1
|
||
container_name: crypto-hermes-migrate
|
||
depends_on:
|
||
postgres:
|
||
condition: service_healthy
|
||
volumes:
|
||
- ./migrations:/migrations:ro
|
||
command:
|
||
- -path=/migrations
|
||
- -database=postgres://${POSTGRES_USER:-postgres}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB:-hermes_market}?sslmode=disable
|
||
- up
|
||
restart: "no"
|
||
|
||
app:
|
||
build:
|
||
context: .
|
||
dockerfile: Dockerfile
|
||
container_name: crypto-hermes-market-gateway
|
||
depends_on:
|
||
postgres:
|
||
condition: service_healthy
|
||
migrate:
|
||
condition: service_completed_successfully
|
||
ports:
|
||
- "${APP_PORT:-8080}:8080"
|
||
environment:
|
||
CONFIG_PATH: /app/config/config.yml
|
||
APP_ENV: ${APP_ENV:-production}
|
||
APP_PORT: ${APP_PORT:-8080}
|
||
POSTGRES_DSN: postgres://${POSTGRES_USER:-postgres}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB:-hermes_market}?sslmode=disable
|
||
BINANCE_BASE_URL: ${BINANCE_BASE_URL:-https://fapi.binance.com}
|
||
# 透传代理:国内直连 fapi.binance.com 不稳,详见 AGENTS.md §7.5
|
||
HTTP_PROXY: ${HTTP_PROXY:-}
|
||
HTTPS_PROXY: ${HTTPS_PROXY:-}
|
||
NO_PROXY: ${NO_PROXY:-}
|
||
volumes:
|
||
- ./config:/app/config:ro
|
||
|
||
volumes:
|
||
hermes_pg_data:
|