Docker Compose — High Availability
Requirements
- An application server that meets the system requirements, with Docker Engine and Docker Compose
- PostgreSQL 15 (14 is supported) with the application and ai-core (
flip_ai_core) databases - Valkey 9 (standalone mode; Sentinel and Cluster are not supported)
- S3-compatible storage with a bucket that allows anonymous read access
- A reverse proxy with SSL termination (nginx, HAProxy or a cloud load balancer)
- Two DNS names (for the application and the MCP server) and certificates for both
- SMTP server credentials
- Outbound HTTPS access to
ai.flip-chart.rufor AI features (ai-core)
Important
The external services must be deployed and reachable over the network from the application server.
Setup steps
1. Files
Use the deploy/docker-compose directory from the delivery archive; replace docker-compose.yaml with the HA version:
# flip on-premise — High Availability
# PostgreSQL, Valkey, S3 storage and the reverse proxy are deployed separately.
# Variables come from the .env file next to docker-compose.yaml
services:
flip-file-handlers:
image: ${FLIP_REGISTRY_IMAGE}/flip-file-handlers:${FLIP_VERSION}
container_name: flip-file-handlers
restart: unless-stopped
volumes:
- ./config/file-handlers/config.yaml:/flip/config/config.yaml:ro
networks:
- flip
flip-ai-core:
image: ${FLIP_REGISTRY_IMAGE}/flip-ai-core:${FLIP_VERSION}
container_name: flip-ai-core
restart: unless-stopped
stop_grace_period: 120s
environment:
POSTGRES_DSN: ${AI_CORE_POSTGRES_DSN}
volumes:
- ./config/ai-core/config.yaml:/flip/cfg/config.yml:ro
networks:
- flip
flip-backend:
image: ${FLIP_REGISTRY_IMAGE}/flip-backend:${FLIP_VERSION}
container_name: flip-backend
restart: unless-stopped
depends_on:
- flip-file-handlers
ports:
- "9000:9000"
volumes:
- ./config/backend/config.yaml:/flip/cfg/config.yaml:ro
# PostgreSQL root certificate for SSLmode: verify-full
# - ./config/backend/ca.pem:/flip/certs/ca.pem:ro
networks:
- flip
flip-frontend:
image: ${FLIP_REGISTRY_IMAGE}/flip-frontend:${FLIP_VERSION}
container_name: flip-frontend
restart: unless-stopped
depends_on:
- flip-backend
ports:
- "8080:80"
volumes:
- ./config/frontend/config.js:/usr/share/nginx/html/app/assets/config.js:ro
networks:
- flip
flip-mcp-server:
image: ${FLIP_REGISTRY_IMAGE}/flip-mcp-server:${FLIP_VERSION}
container_name: flip-mcp-server
restart: unless-stopped
depends_on:
- flip-backend
ports:
- "8090:8090"
volumes:
- ./config/mcp-server/config.yaml:/flip/cfg/config.yaml:ro
networks:
- flip
networks:
flip:
driver: bridgeDownload docker-compose.ha.yaml
The containers publish ports on the host: backend 9000, frontend 8080, mcp-server 8090. ai-core does not publish ports: only the backend calls it over the flip network. If the reverse proxy runs on the same server, you can connect it to the flip network instead of publishing the ports.
2. Environment variables
The .env file sets the image registry and version and the ai-core connection to PostgreSQL:
FLIP_REGISTRY_IMAGE=cr.yandex/crpbj8irels1kqult74e/onpremise
FLIP_VERSION=v1.5.0
AI_CORE_POSTGRES_DSN=postgres://flip:secret-passwd@postgres.example.ru:5432/flip_ai_core?sslmode=requireCreate the flip_ai_core database on the PostgreSQL server in advance:
CREATE DATABASE flip_ai_core OWNER flip;3. Configuration files
Fill in the files in the config directory, specifying the addresses of the external PostgreSQL, Valkey and S3:
| File | Description | Key fields |
|---|---|---|
config/ai-core/config.yaml | AI-core | Auth.Local.Token |
config/backend/config.yaml | Backend | Postgres, RedisClient, S3, Mail, AI, secrets |
config/file-handlers/config.yaml | File-handlers | S3Config, RedisConfig |
config/frontend/config.js | Frontend | API_URL, S3_URL, WEBSOCKET_URL |
config/mcp-server/config.yaml | MCP server | flipApi, RedisClient |
File permissions
Processes in the containers do not run as root. The configuration files must be readable: chmod -R a+rX config.
PostgreSQL over TLS
For an external database, use SSLmode: require or verify-full. For verify-full, mount the root certificate into the container (see the commented-out line in docker-compose.ha.yaml) and set its path in Postgres.SSLRootCert.
4. S3 storage
- Create a bucket and allow anonymous read access to its objects (the
download/public-readpolicy). - Upload the application's media assets: unpack
deploy/sources/s3-assets.tarand upload its contents to the root of the bucket:
mkdir -p s3-assets && tar -xf ../sources/s3-assets.tar -C s3-assets
aws --endpoint-url https://s3.example.ru s3 cp s3-assets s3://flip/ --recursive5. Reverse proxy
Configure routes and timeouts as in the nginx configuration: WebSocket at /app/api/v1/ws, an increased request body limit for /app/api/v1/flip/backup/upload, S3 proxying at /app/s3/, and a separate virtual host for the MCP server.
6. Registry access and startup
cat ../../credentials/authorized_key.json | docker login --username json_key --password-stdin cr.yandex
docker compose pull
docker compose up -d
docker compose psThe application is available at https://example.flip-chart.ru/app. Then proceed to the first launch.