Deployment

Clone and install

git clone <your-fork-of-opensesh>
cd opensesh
pnpm install

The repo is a pnpm workspace; the product lives in apps/web.

Create the Hyperdrive config

Hyperdrive pools and accelerates Postgres connections from the edge:

wrangler hyperdrive create opensesh-db \
  --connection-string="postgres://user:pass@host:5432/opensesh"

Put the returned id into apps/web/wrangler.jsonc under the hyperdrive binding (the binding name is HYPERDRIVE). While you're in that file, also update:

• name — your worker name
• routes — your custom domain (the hosted app uses app.opensesh.io)
• r2_buckets — the FILES binding needs an R2 bucket for speaker uploads (wrangler r2 bucket create opensesh-files)
• send_email — the EMAIL binding for outbound mail
• placement.region — pin the Worker next to your database (for example aws:us-east-1)
• vars — DEMO_MODE (set 0 for a real deployment), MAIL_PROVIDER, MAIL_FROM

Run migrations and seed

Generate and apply the schema from packages/domain (Drizzle), then optionally seed the demo event:

pnpm db:generate
pnpm seed        # optional: demo event + personas

Set secrets

Two secrets, set on the worker:

wrangler secret put BETTER_AUTH_SECRET   # session/token signing — use a long random string
wrangler secret put ANTHROPIC_API_KEY    # optional — enables AI reviews and AI agenda drafts

Deploy

pnpm --filter @opensesh/web deploy
# equivalent to: build + wrangler deploy from apps/web

Point your DNS at the custom domain route and you're live. Subsequent deploys are the same command; migrations are applied against Postgres directly, so run them before deploying schema-dependent changes.