veilrender / deploy /compose-pool.yaml
Peng Ding
fix: deploy-dev compose template token handling, use .env file
39e5cf3
Raw History Blame Contribute Delete
1.23 kB
# Pool mode: VeilRender gateway + separate CloakBrowser workers
#
# Usage:
# docker compose -f deploy/compose-pool.yaml up -d
# docker compose -f deploy/compose-pool.yaml up -d --scale browser-worker=3
#
# Workers use cloakhq/cloakbrowser in CDP server mode (cloakserve).
# VeilRender connects to them via VEILRENDER_WORKERS env var.
# To add more workers, list them comma-separated.
services:
veilrender:
image: oaklight/veilrender:gateway
container_name: veilrender
restart: unless-stopped
ports:
- "7860:7860"
environment:
- VEILRENDER_API_TOKEN=${VEILRENDER_API_TOKEN:-changeme}
- VEILRENDER_RESOURCE_FILTER=true
- VEILRENDER_WORKERS=http://browser-worker:9222
- VEILRENDER_WORKER_MAX_CONCURRENT=${VEILRENDER_WORKER_MAX_CONCURRENT:-5}
- VEILRENDER_WORKER_HEALTH_INTERVAL=${VEILRENDER_WORKER_HEALTH_INTERVAL:-10}
volumes:
- veilrender-data:/data
depends_on:
- browser-worker
deploy:
resources:
limits:
memory: 512M
browser-worker:
image: cloakhq/cloakbrowser
restart: unless-stopped
command: ["cloakserve"]
deploy:
resources:
limits:
memory: 1G
volumes:
veilrender-data: