Files
tiennm99bot/renderer/docs/deployment.md
T
tiennm99 1ee679ad89 fix(deploy): stop exposing renderer tuning as Coolify settings
Coolify lists every ${VAR} that compose.yml references as an app setting,
so the four renderer tuning values showed up as entries to fill in. They
are no longer referenced: the renderer's own defaults apply, and an
override goes into compose.yml as a literal.
2026-10-03 12:11:25 +07:00

1.9 KiB

Deployment

miti99bot compose

The root compose.yml builds this folder as the renderer service and points the bot at it over the compose network. The API has no authentication: it is reachable only from inside that network, so never publish its port or attach a domain to it. The rest of this page covers running the service on its own.

Recommendation

Use a self-hosted/container runtime for v1. Static-only hosts are not enough because /api/gif must render GIF bytes on the server with Remotion.

Good first targets:

  • Coolify Docker app
  • Fly.io
  • Railway
  • Render
  • VPS with Docker
  • Google Cloud Run generic container

Avoid for v1:

  • Cloudflare Workers/Pages
  • pure static Vercel/Netlify deploys

Runtime

Env vars, all optional (defaults shown):

RENDERER_PORT=3000
RENDERER_HOST=0.0.0.0
RENDERER_MAX_CONCURRENT_RENDERS=1
RENDERER_RENDER_TIMEOUT_MS=15000
RENDERER_MAX_OPTIONS=32
RENDERER_MAX_OPTION_CHARS=40

An unset or empty variable uses the default above. The root compose.yml sets only RENDERER_HOST and RENDERER_PORT, so the tuning values use these defaults unless added there.

Start with 1-2 vCPU and 1-2 GB RAM. Increase only after render benchmarks show the service is CPU-bound or concurrency-limited.

Local non-Docker render smoke requires Chrome Headless Shell shared libraries, including libnspr4 and libnss3. Prefer Docker for consistent verification. The Docker image runs npm run browser:ensure during build so production requests do not need to download Chrome Headless Shell on first render.

RENDERER_RENDER_TIMEOUT_MS is a total render timeout. Values below 7000 are raised to 7000 because Remotion's browser timeout has that minimum.

Health

curl http://localhost:3000/api/healthz

Render Test

curl -X POST http://localhost:3000/api/gif \
  -H 'content-type: application/json' \
  --output wheel.gif \
  --data '{"options":["alice","bob","carol"],"winnerIndex":1}'