[cms-sanity] Allow environment configurable dataset

vercel · Oct 22, 2020 · 7460aa8 · 7460aa8
1 parent 585ee90
commit 7460aa8
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/examples/cms-sanity/.env.local.example b/examples/cms-sanity/.env.local.example
@@ -1,3 +1,4 @@
 NEXT_PUBLIC_SANITY_PROJECT_ID=
+NEXT_PUBLIC_SANITY_DATASET=
 SANITY_API_TOKEN=
-SANITY_PREVIEW_SECRET=
+SANITY_PREVIEW_SECRET=
diff --git a/examples/cms-sanity/README.md b/examples/cms-sanity/README.md
@@ -76,6 +76,7 @@ Your `.env.local` file should look like this:
 
 ```bash
 NEXT_PUBLIC_SANITY_PROJECT_ID=...
+NEXT_PUBLIC_SANITY_DATASET=...
 SANITY_API_TOKEN=...
 SANITY_PREVIEW_SECRET=...
 ```

diff --git a/examples/cms-sanity/lib/sanity.js b/examples/cms-sanity/lib/sanity.js
@@ -6,7 +6,7 @@ import {
 
 const options = {
   // Find your project ID and dataset in `sanity.json` in your studio project
-  dataset: 'production',
+  dataset: process.env.NEXT_PUBLIC_SANITY_DATASET || 'production',
   projectId: process.env.NEXT_PUBLIC_SANITY_PROJECT_ID,
   useCdn: process.env.NODE_ENV === 'production',
   // useCdn == true gives fast, cheap responses using a globally distributed cache.