V0 deploy button

Feedback
1

The deploy button in v0 was recently changed so that once you press it it automatically starts deploying.

I wish it was rolled back. so you can see the deployment settings etc. before deploying.

Now I have an issue where I have three different chats in the same project that I want to deploy to different domains, but every time come near the deploy button they overwrite each others deployment. How am I supposed to manage this? How can I deploy different chats in the same v0 project to different domains?

I’m using the chats not as versions but different apps / sites that share environment variables and prompt settings…

1 Like
3

Thanks for the feedback, Simon! I passed it on internally to the v0 team. I will circle back with any additional comments :smile:

The only way to get around this (from what I can see) is creating a new chat outside of that project.

1 Like
4

So here’s a different Feedback if you can give that separately.

This is what I believed chats and projects where for. Create a new chat, to create another app or function, or subpage or something in the same ecosystem that shares environment variabels and system prompts etc.

This would be super handy. Also as a way to organize large projects that could have multiple frontends, abckends and apps etc.

And it all works perfectly for this, except that they all want to replace each other on the same domain. So you’ve just got this last piece missing to treat them as separate deployments, or at least let me just choose which domain I want to deploy to on every individual chat.

1 Like