<aside> 🇵🇸

I do not support the views held by Vercel leadership and their alignment with Israel’s government, and with that, Israel’s genocide of the Palestinian people. I believe in a free Palestine and support the Palestinian people’s right to self-determination. I strongly encourage anyone picking a hosting platform to steer away from Vercel and pick one of the many great alternatives.

</aside>

Getting live on Vercel

  1. Create a new project in Vercel, and click “import” on your newly created copy of the boilerplate. This is probably hosted on Github!

  2. Open up the “Environment Variables” section, copy the entire contents of .env.development and paste it in the first “Key” input in environment variables. You will need to change anywhere it says localhost.

// Change these to the vercel domain
NEXT_PUBLIC_SITE_ROOT="<http://localhost:3000>"
NEXT_PUBLIC_CMS_PREVIEW_URL="<http://localhost:3000/api/preview>"

  1. Click deploy!

  2. After you have a new vercel hosted domain, you’ll want to add that to your Sanity settings as the “Custom studio URL”

<https://sprout-boilerplate.vercel.app/admin>
  1. You’ll need to add a few CORS origins to your API Settings in Sanity. All domains need “Allow Credentials”. If you have a purchased domain connected to your Vercel Deployment, add that too!
<https://sprout-boilerplate.vercel.app>
<https://boilerplate.sprout.store>

// Allows for branch deploys in Vercel
<https://sprout-boilerplate>*.vercel.app
  1. You can add a quick access deploy button in your Sanity admin panel. Click “Deploy” in your dashboard and “Create new target”, you will need the following:

| Vercel Account Token (found here) | Scope: [Your Org] Expiration: [No expiration] | | --- | --- | | Vercel Project ID | Found in Project > Settings |

ISR and Cache Revalidation