- 迁移 000023 gateway.file_objects(personal/system 归属隔离 + 部分索引) - internal/platform/storage:minio-go 适配(端点 scheme 剥离、流式 PutObject/Open/Delete) - internal/workbench/files.go:FileService(sha256 校验、PutObject-then-insert 回滚、delete 先删行再删对象) - admin /api/v1/admin/files + portal /api/v1/portal/files 处理器(流式上传下载、Content-Disposition) - RBAC file:read/file:manage;菜单加文件管理 + 门户文件仓库 - compose 增 minio 服务(S3_* anchor、不暴露端口);nginx client_max_body_size 32m→256m - 管理端文件管理页 + 门户个人文件仓;集成测试 TestFileObjectLifecycle 连真 MinIO 通过 - healthz object_storage:true;README/PRODUCTION/进展文档同步 Co-Authored-By: Claude <noreply@anthropic.com>
2.5 KiB
Production deployment
This bundle builds the Go services and both Art Design Pro applications from source. PostgreSQL, two Redis roles and MinIO (object storage, M8) are included; ClickHouse is not required. MinIO is not a startup dependency: the gateway only warns and refuses file uploads until the bucket is reachable.
Prerequisites
- Docker Engine with Compose v2
- At least 4 CPU cores, 8 GiB RAM and 30 GiB free disk for an initial build
- An external TLS reverse proxy or load balancer
- A backup destination for the PostgreSQL volume
First deployment
Run all commands from the repository root:
cp deploy/production.env.example deploy/production.env
chmod 600 deploy/production.env
# Edit deploy/production.env and replace every CHANGE_ME value.
docker compose \
--env-file deploy/production.env \
-f deploy/docker-compose.production.yml \
config --quiet
docker compose \
--env-file deploy/production.env \
-f deploy/docker-compose.production.yml \
up -d --build
Create the initial administrator once:
docker compose \
--env-file deploy/production.env \
-f deploy/docker-compose.production.yml \
--profile tools run --rm bootstrap-admin
Then remove BOOTSTRAP_ADMIN_PASSWORD from deploy/production.env and use the
admin UI to create database-backed gateway API keys.
Endpoints
- API and OpenAI-compatible gateway:
127.0.0.1:8080 - Admin UI:
http://127.0.0.1:8081/admin/ - Portal UI:
http://127.0.0.1:8082/portal/ - Liveness/readiness:
/healthzand/readyz
Ports bind to loopback by default. Terminate TLS at a reverse proxy and forward
to these endpoints. Change *_BIND_IP only when the host firewall and network
policy are already in place.
Operations
Check status and logs:
docker compose --env-file deploy/production.env -f deploy/docker-compose.production.yml ps
docker compose --env-file deploy/production.env -f deploy/docker-compose.production.yml logs --tail=200 gateway-api
curl --fail http://127.0.0.1:8080/readyz
For upgrades, back up PostgreSQL first, change GATEWAY_VERSION, then run the
same up -d --build command. The one-shot migrator applies forward migrations
before the API starts. Do not use docker compose down -v in production because
it removes persistent data.
The bundled database URLs use sslmode=disable only for the private Compose
network. When using an external PostgreSQL or Redis service, require TLS and use
sslmode=verify-full / rediss:// as supported by that service.