Files
OpenMAIC/docker-compose.yml
T
杨慎 e9d8a33b56 fix(render-service): make parallel capture effective (#1042)
* fix(render-service): make parallel capture effective

* fix(render-service): preserve adaptive workers and beginframe

* fix(render-service): restore adaptive compose sizing
2026-08-04 07:59:43 -04:00

139 lines
6.7 KiB
YAML

services:
openmaic:
build:
context: .
args:
# NEXT_PUBLIC_* values are compiled into the browser bundle. Leave them
# empty unless the corresponding client feature is explicitly enabled;
# persistence and other build-time flags can be supplied on the command line.
- NEXT_PUBLIC_PERSISTENCE=${NEXT_PUBLIC_PERSISTENCE:-}
- NEXT_PUBLIC_PERSISTENCE_TOKEN=${NEXT_PUBLIC_PERSISTENCE_TOKEN:-}
- NEXT_PUBLIC_MAIC_EDITOR_ENABLED=${NEXT_PUBLIC_MAIC_EDITOR_ENABLED:-}
- NEXT_PUBLIC_PI_CHAT_ENABLED=${NEXT_PUBLIC_PI_CHAT_ENABLED:-}
- NEXT_PUBLIC_SHOW_VOCATIONAL_TEST_UI=${NEXT_PUBLIC_SHOW_VOCATIONAL_TEST_UI:-}
- NEXT_PUBLIC_ENABLE_VIDEO_EXPORT=${NEXT_PUBLIC_ENABLE_VIDEO_EXPORT:-}
- NEXT_PUBLIC_VIDEO_EXPORT_CTA_DESTINATION=${NEXT_PUBLIC_VIDEO_EXPORT_CTA_DESTINATION:-}
- NEXT_PUBLIC_ENABLE_PPTX_IMPORT=${NEXT_PUBLIC_ENABLE_PPTX_IMPORT:-}
ports:
- '3000:3000'
env_file:
- .env.local
environment:
# Point the app at the render service when it's running. This wins over any
# RENDER_SERVICE_URL in .env.local; the service only starts under the
# "video-export" profile. The app's capability check probes the service's
# /health, so if the profile is off (service absent) the app reports the
# MP4 export disabled and degrades to the ZIP-download path — this URL
# being set does not, by itself, advertise a working render.
- RENDER_SERVICE_URL=http://render-service:9000
networks:
- default # outbound internet (LLM/media provider APIs, etc.)
- render # reach the render service over the isolated network
volumes:
# Optional: mount server-providers.yml for provider config
# - ./server-providers.yml:/app/server-providers.yml:ro
- openmaic-data:/app/data
restart: unless-stopped
# Optional PostgreSQL backing for the app-embedded persistence API.
# The app reads DATABASE_URL and PERSISTENCE_DEV_TOKEN from .env.local; keeping
# those values there avoids changing the default browser-only deployment.
postgres:
image: postgres:16
profiles:
- server-persistence
environment:
- POSTGRES_DB=openmaic
- POSTGRES_USER=openmaic
# Development default only. Override this and the matching DATABASE_URL
# before using the stack outside a local trusted environment.
- POSTGRES_PASSWORD=${PERSISTENCE_POSTGRES_PASSWORD:-openmaic-dev}
healthcheck:
test: ['CMD-SHELL', 'pg_isready -U openmaic -d openmaic']
interval: 5s
timeout: 5s
retries: 10
start_period: 5s
volumes:
- openmaic-postgres:/var/lib/postgresql/data
restart: unless-stopped
# Isolated MP4 render service (Node 22 + Chromium + FFmpeg) for classroom video
# export (issue #866). Opt-in: only starts with `--profile video-export`, since
# the image is heavy (bundles Chromium + FFmpeg) and the capability is optional.
#
# docker compose --profile video-export up --build
#
# Sits on the `render` network (`internal: true`, no host/internet gateway).
# It shares that network with `openmaic` only so the app can reach it; to stop
# the untrusted Chromium from initiating connections *back* to the app over
# that shared network, the container's entrypoint installs an iptables egress
# lockdown (needs CAP_NET_ADMIN) that drops all outbound except loopback and
# replies on app-initiated connections. The export ZIP is self-contained, so
# the render needs no outbound at all.
render-service:
build: ./render-service
profiles:
- video-export
expose:
- '9000'
# Required for the entrypoint's iptables egress lockdown. Without it the
# service still boots, but logs a warning and does NOT block Chromium egress.
cap_add:
- NET_ADMIN
environment:
- PORT=9000
# Keep the beginFrame-capable browser path available when producer decides
# the cgroup has enough memory. Under this service's 4 GiB limit producer's
# automatic low-memory profile safely selects screenshot capture + one
# worker instead of multiplying Chromium for unvalidated 1080p/4K renders.
- PRODUCER_BROWSER_GPU_MODE=hardware
- PRODUCER_HEADLESS_SHELL_PATH=/usr/bin/chromium-headless-shell
- RENDER_MAX_CONCURRENCY=1
- RENDER_MAX_CONCURRENT_EXTRACTIONS=1
# Producer's browser pool shares a Chromium compositor across capture
# sessions. Keep it disabled so an operator who raises memory and opts into
# parallel capture gets independent browsers; the 4 GiB default resolves to
# one worker, so this does not multiply memory by itself.
- PRODUCER_ENABLE_BROWSER_POOL=false
# Leave producer workers unset: producer 0.7.60 applies its cgroup memory,
# CPU, small-job, low-memory, and capture-cost guards. Operators may opt
# into the measured 720p latency profile documented in the service README.
# Long compositions still need CDP headroom even with one adaptive worker.
- PRODUCER_PUPPETEER_PROTOCOL_TIMEOUT_MS=900000
# OpenMAIC's long slide exports currently exhaust producer's 15s static
# verification budget and disable dedup anyway. Skip that guaranteed-lost
# startup cost until the verifier can share/scale its plan across workers.
- HF_STATIC_DEDUP=false
# In this default topology the app is exposed directly and does NOT set
# TRUST_PROXY_HEADERS, so every caller collapses to one identity. A
# per-identity limit would then throttle the whole deployment to a single
# render, so disable it here and rely on RENDER_MAX_CONCURRENCY + the global
# RENDER_MAX_QUEUE cap. Set this >0 only with a trusted proxy supplying
# per-user identity (see render-service/README.md).
- RENDER_MAX_JOBS_PER_USER=0
# Bound RAM: each render (Chromium + FFmpeg + archive expansion) is memory
# heavy, and extraction is capped separately (RENDER_MAX_CONCURRENT_EXTRACTIONS).
# Raise for higher RENDER_MAX_CONCURRENCY / larger classrooms.
mem_limit: 4g
# Chromium media/frame work can exceed Docker's 64 MiB default shared-memory
# mount. This is a ceiling inside the same 4 GiB cgroup, not eager allocation.
shm_size: 2gb
networks:
- render
restart: unless-stopped
networks:
default: {}
# Isolated network for app <-> render-service traffic. `internal: true` means
# no route to the host or internet. Both services share it so the app can
# reach the render service; the render container additionally blocks its own
# egress (iptables, see the service's entrypoint) so the untrusted Chromium
# can't use this shared network to reach the app.
render:
internal: true
volumes:
openmaic-data:
openmaic-postgres: