Deploying v3 of a project without impacting data or causing downtime.

6 replies
Last updated: Aug 31, 2023
Hey all! I have an upgrade/deploy question: I had a project that was v2, and instead of upgrading the studio to v3, which was causing me some issues, I just created a new one using v3. I need to deploy it now, and the new one is pointing at the prior dataset, so my question is this: if I deploy the v3 with the same projectId as the v2, will everything work? I don't imagine it'll impact the data since I've been pointing at the remote datasource from my local, but want to confirm whether I have to do anything special for the deploy.
It's an active client project, so I don't want to introduce any downtime.

Aug 31, 2023, 1:56 PM
It shouldn’t affect your content at all. It sounds like you’ve got a good grasp of the situation, the studio is “just another web app” interacting with content from the Content Lake that has a few more permissions than your public facing web app (like modifying/updating).
So the actual action of deploying the studio itself shouldn’t interfere with the relationship between the content lake and your client’s production web app.
Aug 31, 2023, 2:53 PM
Excellent, thanks!
Aug 31, 2023, 2:54 PM
If you’ve got it all running locally and are happy with it, and deploy with the same configuration, you should be good to go.
Aug 31, 2023, 2:54 PM
Sweet, that's what I was hoping.
Aug 31, 2023, 2:55 PM
Appreciate the confirmation!
Aug 31, 2023, 2:55 PM
Aug 31, 2023, 2:55 PM

Sanity– build remarkable experiences at scale

The Sanity Composable Content Cloud is the headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?