Understanding dev deployments
This is a very newbie question but I searched the docs and couldn’t find an obvious answer.
We have a team of three of us that are going to be working on our convex app. Previously it was just me, but I invited the others to the project and told them to grab the code, provided a copy of my .env.local and got them to run npx convex dev.
One thing I noticed it created a new development deployment for that person, despite my env containing a specific dev deployment.
Couple questions:
Is there a specific best practices regarding us sharing/having our own development deployments?
After a bit of faff we managed to get connected to my dev instance for the 2nd dev. Is there any issues with this inherently? We recently set up better-auth and are using the Microsoft entry connector, and ideally don’t want to have to maintain 3 (4 including production) different redirect URIs if it’s unnecessary, as well as the database in the database ideally would be consistent for the three of us.
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
The problem with sharing a single dev deployment is that two engineers can't really work at the same time. Remember that the dev deployment isn't just the data in the database, it's the code. With Convex you develop with
npx convex dev running, so every time you save your types are regenerated and your changes are deployed. If two engineers are doing this at the same time they're constantly overwriting each other's code.
If it's a matter of keeping multiple redirect uri's, fwiw, that's a pretty low overhead, "set it and forget it" configuration. If you want to keep data relatively synced, imports and exports work for that. But yeah, you want each engineer to have their own dev deployment.I thought about that as I was typing it. That’s a very good point. The data overheard is more annoying but if we can import/export that solves that problem honestly.
Thanks - super helpful.