using projects as deployments
❔Advice
We are getting about to deploy Convex, switching from Neon, and honestly there are a lot of things to love about Convex, but Neon's system of managing deployments and branching seems way more straightforward. We would rather just have different named environments that we can easily create and deploy to. But Convex only allows one "prod" deployment per project apparently, and preview deployments behave oddly, e.g. changing their URL and deleting your data each time you push to your branch. So we are thinking about just using lots of projects and mostly using one deployment per project (except maybe for dev environments, but even for them it would be nice if dev environments were not linked to developers but each developer could just use whichever dev environments they wanted whenever they wanted and they would work similarly to prod environments). Have others encountered these issues? Any chance Convex will release a less opinionated deployment system that doesn't force its particular way of working on us?
