Next.js App Vercel Deployment Setup
Budget: £20 – £250 GBP
I have a Next.js project sitting in a private GitHub repo and an active Vercel account that’s still waiting for its first deployment. What I need is a smooth, one-time setup that leaves everything ready for continuous delivery.
Here’s the exact flow I’d like you to handle:
• Connect my GitHub repository to Vercel so each push to main triggers a build.
• Keep the default build command (next build) and be sure the build runs on Node 18 —or whichever LTS Vercel currently tags as latest.
• Copy every environment variable listed in Section 3 of the repo’s README into the Vercel project settings (names and values must match precisely).
• On your local machine run npx prisma db push once against my MongoDB Atlas cluster; this creates the necessary collections and indexes before the first cloud build.
• Kick off an initial Vercel deployment and verify that the app boots without runtime errors.
Success is simple: the deployment finishes green, the live URL loads the app correctly, and subsequent pushes rebuild automatically. If anything in the pipeline fails, I expect concise notes on the fix so the workflow remains solid going forward.
Here’s the exact flow I’d like you to handle:
• Connect my GitHub repository to Vercel so each push to main triggers a build.
• Keep the default build command (next build) and be sure the build runs on Node 18 —or whichever LTS Vercel currently tags as latest.
• Copy every environment variable listed in Section 3 of the repo’s README into the Vercel project settings (names and values must match precisely).
• On your local machine run npx prisma db push once against my MongoDB Atlas cluster; this creates the necessary collections and indexes before the first cloud build.
• Kick off an initial Vercel deployment and verify that the app boots without runtime errors.
Success is simple: the deployment finishes green, the live URL loads the app correctly, and subsequent pushes rebuild automatically. If anything in the pipeline fails, I expect concise notes on the fix so the workflow remains solid going forward.