Plans for new Deployment type between 'Dev' and 'Production'?
Hi there, forgive me if this has already been asked.
Currently, our 'Testflight' setup consists of creating an entirely new project to act as the database for this, however this doesn't feel like a clean solution as it would be nicer if there was one more designated Deployment option from the existing ones.
The 'Preview deployments' don't exactly match what we need and I understand from the docs it does mention this is the best solution (https://docs.convex.dev/production#staging-environment: 'If you need a more permanent staging environment, you can use a separate Convex project, and deploy to it by setting the CONVEX_DEPLOY_KEY environment variable when running npx convex deploy'), but again it would be nice to have everything contained within one project so we wouldn't have to update environment variables in both projects for example.
Are there any plans to add anything like this in the future or will this remain the best method to use? Thanks 🙏
Deploying Your App to Production | Convex Developer Hub
Convex is built to serve live, production app traffic. Here we cover how to
2 Replies
I’m wondering why the environment variables pose an issue here. You can automate setting environment variables via cli within your GitHub action (assuming you’re referencing setting environment variables for the convex project). Can you share a little more about what you’re running into?
Sorry for the late response and confusion, I was unaware we could set the environment variables from the CLI for a given project. However the same idea still stands, here's some more context:
- Right now in our main Convex project, we have the "Development" deployment which we use locally for testing, as well as the "Production" deployment for production.
- If we want to have our app go to "Testflight" for internal testing, we don't have a separate Convex deployment for this, so we would have to choose between "Production" and "Deployment" to use as the "Testflight" database. We want a more permanent deployment here that allows "Testflight" and "internal testing" on Android to have their own database.
- Right now the only option is to have two separate Convex projects:
- "Project A" for the "Development" and "Production" databases
- "Project B" for this "Testflight" database
- This is fine but it doesn't feel like a "clean" solution as intuitively it feels like separate projects are for separate apps (if that makes sense)
It would be nice to have one more Convex deployment for this stage of development, so that we could have a separate database for Testflight, and so when we run migrations on the database to test new features, it doesn't mess with our Production