Deploy (Node) - Streamly

Use this path when you want a classic Node process behind Nginx, Caddy, or your host’s load balancer. For the production edge path used at streamly.watch, see Deploy Cloudflare.

When to use this

Goal	Use
VM / bare metal / Node PaaS	This guide (Option A)
Docker / OCI	Option B below
Vercel	Deploy (Vercel)
Cloudflare Workers	Deploy Cloudflare

Option A — Node.js server

corepack enable
pnpm install --frozen-lockfile
pnpm run build
PORT=3000 pnpm run start

Set process env (see Environment Variables). Preserve Host and forwarded-protocol headers on the reverse proxy.

Option B — Docker / OCI

docker build \
  --build-arg NEXT_PUBLIC_APP_URL=https://streamly.example \
  --build-arg NEXT_PUBLIC_PLATFORM_HOST=streamly.example \
  --build-arg NEXT_PUBLIC_STREAMLY_API_BASE=https://streamly.example/api/v1 \
  --build-arg NEXT_PUBLIC_SUPABASE_URL=https://PROJECT.supabase.co \
  --build-arg NEXT_PUBLIC_SUPABASE_ANON_KEY=PUBLIC_ANON_KEY \
  -t streamly-platform .

docker run --rm -p 3000:3000 \
  --env-file /secure/path/streamly-runtime.env \
  streamly-platform

Only pass NEXT_PUBLIC_* as --build-arg. Keep service-role, encryption, cron, email, and plugin secrets in the runtime --env-file.

Scheduled jobs (Node / Docker)

POST /api/internal/jobs/run
X-Streamly-Cron-Secret: <STREAMLY_CRON_SECRET>
Content-Type: application/json

Supported payloads:

{"job":"maintenance"}
{"job":"provider_health"}
{"job":"metadata_sync"}
{"job":"smart_sync"}

smart_sync warms popular catalog pages. There is no domain_sync job (custom-domain SaaS was removed).

After deploy

Check	Expect
`/`	Storefront loads
`/admin/login`	Operator email + password sign-in
`/api/docs`	OpenAPI available
Host / slug tenants	Platform host + `{slug}.…` resolution (Domain)