Deployment

Deployment Model

Bunship is a TurboRepo monorepo.
Production is deployed as one site (apps/ship) that serves:

• Marketing pages
• App workspace
• Admin pages
• Docs routes and docs search API
• API routes under /api/v1/*

No separate docs deployment is required.

1. Required Env Vars (Copy First)

Generate a secret first:

openssl rand -base64 32

Use this as a baseline production env set:

# Core auth + app URLs
BETTER_AUTH_SECRET="replace-with-long-random-secret"
AUTH_SECRET="replace-with-long-random-secret"
BETTER_AUTH_URL="https://YOUR_DOMAIN"
NEXT_PUBLIC_SITE_URL="https://YOUR_DOMAIN"
NEXT_PUBLIC_SERVER_URL="https://YOUR_DOMAIN"
NEXT_PUBLIC_API_PREFIX="/api/v1"
ADMIN_EMAIL_LIST="admin@YOUR_DOMAIN"
EMAIL_FROM="Bunship <noreply@YOUR_DOMAIN>"

# OAuth
OAUTH_GITHUB_CLIENT_ID="xxx"
OAUTH_GITHUB_CLIENT_SECRET="xxx"
OAUTH_GOOGLE_CLIENT_ID="xxx"
OAUTH_GOOGLE_CLIENT_SECRET="xxx"
NEXT_PUBLIC_OAUTH_GOOGLE_CLIENT_ID="xxx"

# Database + mail
DATABASE_URL="postgresql://..."
RESEND_API_KEY="re_xxx"

# Stripe
STRIPE_SECRET_KEY="sk_live_xxx"
STRIPE_WEBHOOK_SECRET="whsec_xxx"

# Storage (S3-compatible / R2)
S3_ENDPOINT="https://<account>.r2.cloudflarestorage.com"
S3_REGION="auto"
S3_ACCESS_KEY="xxx"
S3_SECRET_KEY="xxx"
S3_BUCKET="your-bucket"
NEXT_PUBLIC_S3_URL_BASE="https://cdn.YOUR_DOMAIN"

# Misc required by current validators
S_GITHUB_PERSONAL_ACCESS_TOKEN="ghp_xxx"
CLOUDFLARE_ACCOUNT_ID="xxx"

Setup references:

• Better Auth docs: https://www.better-auth.com/docs/introduction
• Clerk docs: https://clerk.com/docs
• GitHub OAuth app: https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app
• Google OAuth: https://developers.google.com/identity/protocols/oauth2
• Stripe keys + webhook: https://docs.stripe.com/keys, https://docs.stripe.com/webhooks
• Resend API keys: https://resend.com/docs
• Full env list in this repo: /en/docs/operations/env-config

2. Vercel Deployment (TurboRepo)

Because this repo is TurboRepo-based, there are two valid setups.

Option A (Recommended): Turbo Root Mode

Use the repository root as Vercel Root Directory.

Why this mode: clearer monorepo behavior, better with Turbo dependency graph and cache.

Option B: App Root Mode

If you keep Root Directory = apps/ship, use:

After deploy, configure Stripe webhook endpoint:

https://YOUR_DOMAIN/api/v1/webhook/stripe

Vercel references:

• Monorepo guide: https://vercel.com/docs/monorepos
• Build settings: https://vercel.com/docs/builds/configure-a-build
• Turbo filtering: https://turbo.build/repo/docs/crafting-your-repository/running-tasks#using-filters

3. Cloudflare Deployment (OpenNext)

This repo already includes OpenNext Cloudflare config (apps/ship/open-next.config.ts + apps/ship/wrangler.jsonc).

Run from repo root:

bun install
cd apps/ship
bunx wrangler login
bun run deploy

bun run deploy executes:

1. opennextjs-cloudflare build
2. opennextjs-cloudflare deploy

Cloudflare references:

• OpenNext Cloudflare docs: https://opennext.js.org/cloudflare
• Wrangler config: https://developers.cloudflare.com/workers/wrangler/configuration/
• Secrets/variables: https://developers.cloudflare.com/workers/configuration/secrets/

4. One-Click Deployment Checklist

Vercel

• Import Git repo
• Choose Option A or Option B settings above
• Add required env vars
• Deploy
• Add Stripe webhook endpoint
• Run smoke tests below

Cloudflare

• Create/choose Workers project
• Add required env vars/secrets
• bun install
• cd apps/ship && bun run deploy
• Bind custom domain
• Run smoke tests below

5. Post-Deploy Smoke Test

• /:locale/docs
• /:locale/signin
• /:locale/subscription
• /:locale/admin
• /api/v1/health (if enabled)
• /api/docs/search