Deployment

Vercel auto-detects Next.js, and the shipped vercel.json files declare the workspace-aware build commands.

{
  "buildCommand": "cd ../.. && pnpm build --filter=@syntaxkit/web",
  "installCommand": "pnpm install",
  "framework": "nextjs"
}

Two Fly apps, one per Next.js app, both built from the kit's Dockerfiles. The web app's release hook handles migrations automatically.

fly launch --copy-config --no-deploy

[deploy]
  release_command = '/bin/sh /release/scripts/deploy/migrate-database.sh'

cd apps/docs && fly launch --copy-config --no-deploy

fly secrets set \
  DATABASE_URL="postgresql://..." \
  BETTER_AUTH_SECRET="$(openssl rand -base64 32)" \
  STRIPE_SECRET_KEY="sk_live_..." \
  STRIPE_WEBHOOK_SECRET="whsec_..." \
  GITHUB_CLIENT_ID="..." \
  GITHUB_CLIENT_SECRET="..." \
  --app syntaxkit-web

fly deploy

Render reads the kit's render.yaml blueprint at the repo root and provisions both services in one click. Migrations run as a preDeployCommand on every release.

The docker-compose.yml at the repo root defines three services: a one-shot migrator (in the tools profile), web, and docs. Buyers bring their own Postgres.

cp .env.docker.example .env
docker compose build
docker compose run --rm migrator
docker compose up -d

The migrator service uses the tools profile so it doesn't run with up; invoke it explicitly before each release. Web and docs both ship healthchecks (/api/healthz for web, / for docs), and web is configured with a 30-second stop_grace_period so Next.js after() callbacks can finish before SIGTERM.

Pre-built images on GHCR. .github/workflows/docker.yml publishes the same images to GHCR on every push to main and every semver tag:

• ghcr.io/<owner>/<repo>/web:latest (and :<sha>, :<branch>, :<version>)
• ghcr.io/<owner>/<repo>/docs:latest

Useful for Kubernetes, Coolify, Dokku, Nomad, or any other Docker host. Pull the image, set runtime env, and run migrations either by building the migrator stage (docker build --target migrator ...) or by invoking scripts/deploy/migrate-database.sh from a job container that has Prisma available.

The kit ships no netlify.toml, but Netlify, Railway, Heroku, Coolify, and other generic Next.js hosts run the kit cleanly using the same shape as Vercel:

• Build the workspace via pnpm build --filter=@syntaxkit/web (or --filter=@syntaxkit/docs), with pnpm install as the install command.
• Set the same build-time vs runtime env split documented above.
• Run migrations from CI before the deploy step. scripts/deploy/migrate-database.sh works on any Linux host with Node and the packages/database workspace available.

Each platform declares those settings its own way (Netlify uses netlify.toml, Railway uses dashboard config); refer to your host's Next.js setup guide for the exact syntax.

Generate with openssl rand -base64 32 and set the same value on every replica. Without a shared key, a server-action signature created by replica A can't be decrypted by replica B, and you'll see intermittent failures on form submissions that span multiple requests.

Set TRUST_PROXY_HEADERS=true and TRUSTED_PROXY_IP_HEADERS=x-forwarded-for. Better Auth uses these to see the real client IP through the proxy. Render's blueprint sets them by default; on Fly's edge-only setup they aren't needed.

Only when Better Auth needs a different origin from NEXT_PUBLIC_APP_URL. Most deployments leave it unset and let Better Auth derive its base URL from the public app URL.