ForkDocs
Self-host

Deployment

Deploying the main app and the documentation site.

Main Fork app (apps/web)

Deploy as a Next.js application with root directory apps/web.

  • Install from the monorepo root: bun install (so workspace resolution works).
  • Build using the web package scripts (e.g. bun run build from root with Turbo filtering to web, or the equivalent in CI).

Ensure production environment variables match Environment variables.

Documentation (apps/docs)

The docs site is a separate Next.js app. Typical setup:

  • Root directory: apps/docs
  • Install: from monorepo root with bun install
  • Build: per apps/docs/package.json (e.g. bun run docs:build from root)

A common production hostname is docs.fork.video (configure DNS and your host accordingly).

Turborepo / Vercel

Turborepo coordinates builds. On Vercel, link the project to enable Remote Cache for faster CI and team builds.

Local cache hit rates for next build are often limited because Next and Fumadocs emit generated files each run; remote cache still helps when inputs are unchanged.

On this page