Skip to content

VERCEL.md

Latest commit

 

History

History
65 lines (42 loc) · 3.79 KB

VERCEL.md

File metadata and controls

65 lines (42 loc) · 3.79 KB

Deploying on Vercel

Why Postgres

Vercel’s serverless runtime does not support a durable on-disk SQLite file. This project uses PostgreSQL so API routes can persist tasks and logs.

Steps

  1. Create a database

    • Neon (free tier) or any Postgres host.
    • Copy the connection string (use SSL where required, e.g. ?sslmode=require).

  2. Connect the GitHub repo in Vercel and add environment variables:

    Name Required Notes
    DATABASE_URL Yes Postgres URL (Neon pooled or direct). If prisma migrate deploy times out (P1002), use Neon’s direct URL for builds or run migrations locally.
    OPENAI_API_KEY Optional If unset, users can use BYOK in the app
    TASKHUB_TIMEZONE Optional e.g. America/New_York
    NEXT_PUBLIC_APP_URL Recommended Your site URL (used in playbook assignment emails/SMS). Vercel: https://<project>.vercel.app
    RESEND_API_KEY Optional Department playbooks: email workers their checklist link
    RESEND_FROM_EMAIL Optional Verified sender, e.g. Task Hub <noreply@yourdomain.com>
    TWILIO_* Optional Playbooks SMS: TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_FROM_NUMBER

    Neon: Pooled is fine for the running app. If migrations fail on the pooler host, switch DATABASE_URL to the direct connection for the deploy step or run npx prisma migrate deploy from your machine with the direct URL.

  3. Deploy
    The build runs prisma migrate deploy && next build, which applies migrations to your database and then builds Next.js.

  4. Neon + Prisma
    For connection pooling with Neon, you may use their pooled URL and Prisma’s recommended query params.

Build stuck on prisma generate

  • Ensure DATABASE_URL is set for Production (and Preview if you use preview deploys) in Vercel before the build runs.
  • postinstall runs prisma generate, which needs DATABASE_URL present in the environment so the schema can be resolved.

Error P1002 — timed out (Neon)

Usually means prisma migrate deploy is using the pooler. Use Neon’s direct connection string for the step that runs migrations (e.g. set DATABASE_URL to direct in the Vercel build env, or run npx prisma migrate deploy locally with the direct URL).

Error P1012 — URL must start with postgresql://

This means Vercel’s DATABASE_URL is missing, empty, or not a Postgres URL (e.g. still file:./dev.db, or broken).

  1. Vercel → your project → Settings → Environment Variables.
  2. Add or fix DATABASE_URL:
    • Value must start with postgresql:// or postgres:// (Neon’s connection string does).
    • Paste only the URL — do not wrap the whole value in extra " " quotes in the UI (no "postgresql://..." as the stored value).
  3. Apply to Production and Preview if you build previews.
  4. Redeploy after saving.

Local builds use .env; ensure that file has a Postgres URL too (not SQLite).

Migrating from an old SQLite checkout

If you previously used file:./dev.db, switch .env to a Postgres URL, run npx prisma migrate dev locally once, and redeploy.

Node.js version

This repo pins Node 20 LTS via package.json → engines and .nvmrc. Vercel uses engines.node for installs and builds—avoid Node 24 unless you have a specific need.

Skew Protection (dashboard)

Skew Protection must be turned on in the Vercel project UI (not in this repo): Project → Settings → Runtime / Deployment Protection (wording varies). Enable it to reduce mismatches between a new deployment’s server and an old tab still running previous client JS after a deploy.