Skip to main content

Knowledge > Runbooks > Deployment > Deploy churchwiseai-web

Deploy churchwiseai-web to Production

Deploy changes to churchwiseai.com (which also serves sermonwise.ai and sharewiseai.com) via Vercel's git-based continuous deployment.

Prerequisites

  • Write access to the churchwiseai-web GitHub repo
  • pnpm installed locally
  • vercel CLI logged in (vercel whoami should return churchwiseai-5386)
  • gh CLI logged in
  • Working directory: C:\dev\churchwiseai-web\

Steps

  1. Create a feature branch from the current deploy branch

    cd /c/dev/churchwiseai-web
    git checkout main && git pull
    git checkout -b feat/<short-description>
  2. Make your changes, then verify the build passes locally

    pnpm build

    Fix all TypeScript errors, lint errors, and build failures before proceeding.

  3. Stage and commit your changes

    git add <specific-files>
    git commit -m "feat: describe your change"
  4. Push the feature branch to GitHub

    git fetch origin && git pull --rebase
    git push -u origin feat/<short-description>

    Vercel automatically creates a preview deployment for every pushed branch. The preview URL will appear in the GitHub PR checks.

  5. Open a pull request (optional but recommended)

    gh pr create --title "Your change title" --body "Description of changes"
  6. Verify the preview deployment

    • Open the Vercel preview URL from the PR checks or vercel ls
    • Test the specific pages you changed
    • Test: / (homepage), /pricing, /chatbot, /voice
    • If the preview fails, fix locally and push again
  7. Merge to main to trigger production deploy

    git checkout main && git pull
    git merge feat/<short-description>
    git push

    Do NOT use git push --force.

  8. Monitor the production deployment

    vercel logs --tail --project churchwiseai-web

    Watch for runtime errors during and after deploy. Deployment typically takes 60–90 seconds.

  9. Smoke test production

Verification

Confirm the deployment succeeded:

vercel ls --project churchwiseai-web

The top entry should show "Production" with a timestamp within the last few minutes and status "Ready".

Rollback

If the production deploy is broken, see rollback.md.

See Also

  • rollback.md — how to revert a bad deploy
  • env-var-rotation.md — if a secret needs updating
  • C:\dev\churchwiseai-web\CLAUDE.md — project-specific build instructions