Multiple environments and studios in Sanity Studio setup.

Hi,
we have set up our Sanity Studio like this, companyname.sanity.studio - 4 datasets:
Dev
QA
Stag
Prod

But we found out that when doing changes to the studio in one dataset it changes to all datasets in the same Studio.

Now
tells me we need 4 different environments and studios to avoid this, is this how Sanity has built this?
We only use this for one website, so I think it is a bit strange to have 4 different projects.

Please explain how you have built this. Thanks

At Gorillas, we do use 2 different projects for the 2 environments of the same website, indeed. And we have a script to backport production data onto the development environment to make it easier to work on actual data.

But we found out that when doing changes to the studio in one dataset it changes to all datasets in the same Studio.

Could you elaborate on this? Are you saying that changes you make in the studio is reflected in all datasets? (The studio can’t do requests to multiple datasets at once)

- will elaborate on this.

There are different ways of slicing and dicing projects/datasets/studios. The most common way is to have one studio, one project, and use datasets for dev/staging/prod environments.
In these cases, it’s often better to deploy the studio to another hosting solution (like Vercel or Netlify) and use environment variables to control its dataset configuration. Then you can access the studio on

dev|qa|taging.domain.tld/studio

or something along those lines.

Yeah, that is what I was hoping for also.

let me correct the question a bit, so we have 4 datasets that we have created for seperate environments. but as sanity only has one studio instance. any dev change that we do to sanity scheme is reflected in studio before even getting qa tested. so my proposed solution is to host multiple sanity studio instances so that devs can do changes and deploy to that particular env to test without changing the production schema

I see. Then I’d look at hosting the studio on e.g. Vercel that also supports PR and branch deployments. This is what we do internally at Sanity 🙂

yup. thank you. this is whats proposed internally from our dev team as well. 🙂

Our

sanity.studio

hosting is made for simple use cases to get started quickly.

Great. We are using Vercel as well

Here’s an example. https://github.com/sanity-io/structured-content-2022/blob/main/studio/sanity.json

So we move the studio hosting to vercel, then it will be resolved. Any good resources on migration or moving or is it easy peasy?

We also made a small thing in the logo that reflects the environment: https://github.com/sanity-io/structured-content-2022/blob/main/studio/plugins/structured-content-logo/Logo.tsx

It should be enough to point Vercel to the studio repo. It should have automatic config support

its fairly straightforward process to deploy sanity in Vercel

Great stuff, thanks for your quick feedback Knut 👍

Thank You again for quick support and feedback. 🙂

We’ve done the env-based logo as well, it’s good!
https://twitter.com/KittyGiraudel/status/1387720408745627651?s=20&t=nY6jioi-0LodFOl60RjdGg