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.
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.
