Skip to content

feat: vercel prod docs#68

Merged
evan-taylor merged 1 commit intodevfrom
evan/vercel-prod-docs
Apr 9, 2026
Merged

feat: vercel prod docs#68
evan-taylor merged 1 commit intodevfrom
evan/vercel-prod-docs

Conversation

@evan-taylor
Copy link
Copy Markdown
Collaborator

@evan-taylor evan-taylor commented Apr 9, 2026

Linked Issues

Closes #
Linear: (e.g., POLY-123)

Summary

Briefly explain the change and why.

How to Test

Steps to verify locally:

  • npm run lint
  • npm run typecheck
  • npm test
  • Manual flow:
    1. npm run dev:backend (in terminal A)
    2. npm run dev (in terminal B)
    3. Verify the change: <describe expected behavior/screens>

Checklist

  • Tests added/updated (if applicable)
  • Lint/tests pass locally (npm run lint)
  • Docs updated (README/ADR/changelog if needed)
  • Follows conventional commit format
  • No merge conflicts with dev

Screenshots / Demos

(if UI or visible behavior - attach images, videos, or GIFs)

Summary by CodeRabbit

  • Documentation

    • Added comprehensive guide for Vercel deployment with backend integration, including setup instructions, required configuration, and deployment checklist.
  • Chores

    • Updated environment variable templates with necessary configuration parameters, implemented new build coordination script for Vercel, and updated deployment pipeline configuration.

@evan-taylor evan-taylor merged commit 7f2f37b into dev Apr 9, 2026
1 of 2 checks passed
@evan-taylor evan-taylor deleted the evan/vercel-prod-docs branch April 9, 2026 07:02
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 9, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f9eed370-e14b-451f-bc3f-8a2ce7dc0d04

📥 Commits

Reviewing files that changed from the base of the PR and between 5c7ff7d and 139e2f5.

📒 Files selected for processing (6)
  • README.md
  • backend/.env.example
  • docs/VERCEL_CONVEX_DEPLOYMENT.md
  • frontend/.env.example
  • package.json
  • vercel.json

📝 Walkthrough

Walkthrough

This pull request adds Vercel and Convex deployment documentation and configuration. It introduces a new build:vercel npm script that orchestrates Convex backend deployment with frontend building, updates environment variable examples across backend and frontend, creates comprehensive deployment guidance, and modifies the Vercel build command to use the new orchestration script.

Changes

Cohort / File(s) Summary
Documentation & Deployment Guide
README.md, docs/VERCEL_CONVEX_DEPLOYMENT.md
Added reference link in README and created comprehensive deployment guide covering Vercel project settings, environment variables, Convex configuration, production rollout checklist, preview deployments, and auth callback URL requirements.
Environment Configuration
backend/.env.example, frontend/.env.example
Added CONVEX_URL and CONVEX_SITE_URL to backend example (with documentation explaining their purpose), and updated EXPO_PUBLIC_CONVEX_URL comment in frontend example to clarify Vercel build-time injection.
Build & Deployment Scripts
package.json, vercel.json
Added build:vercel npm script that deploys Convex backend and builds frontend in sequence, and updated Vercel's buildCommand to invoke the new orchestration script instead of building frontend directly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • jaydonkc

Poem

🐰 A hop, a skip, through Convex clouds we go,
Vercel's helper sets the stage aglow,
Backend deploys, the URL takes flight,
Frontend builds bright—deployment done right!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch evan/vercel-prod-docs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant