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-webGitHub repo pnpminstalled locallyvercelCLI logged in (vercel whoamishould returnchurchwiseai-5386)ghCLI logged in- Working directory:
C:\dev\churchwiseai-web\
Steps
-
Create a feature branch from the current deploy branch
cd /c/dev/churchwiseai-webgit checkout main && git pullgit checkout -b feat/<short-description> -
Make your changes, then verify the build passes locally
pnpm buildFix all TypeScript errors, lint errors, and build failures before proceeding.
-
Stage and commit your changes
git add <specific-files>git commit -m "feat: describe your change" -
Push the feature branch to GitHub
git fetch origin && git pull --rebasegit 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.
-
Open a pull request (optional but recommended)
gh pr create --title "Your change title" --body "Description of changes" -
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
- Open the Vercel preview URL from the PR checks or
-
Merge to main to trigger production deploy
git checkout main && git pullgit merge feat/<short-description>git pushDo NOT use
git push --force. -
Monitor the production deployment
vercel logs --tail --project churchwiseai-webWatch for runtime errors during and after deploy. Deployment typically takes 60–90 seconds.
-
Smoke test production
- https://churchwiseai.com — homepage loads, no console errors
- https://churchwiseai.com/pricing — pricing grid renders correctly
- https://sermonwise.ai/sermons — hostname rewrite works
- https://churchwiseai.com/admin/[a-known-token] — admin dashboard accessible
- Check browser console for JavaScript errors
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