Vercel Environments and Neon Branches
Is it possible to have the following work with Vercel and Neon with GitHub Actions?
Neon branches:
- main (production)
- staging
- [preview branches]
Vercel environments:
- production
- staging
- [previews]
My idea would be to have two "static" environments (production and staging) that never change connection strings but the previews are always being created and deleted. How does that work with GitHub Actions? Does the workflow need to drop/add DB_URL environment variables anytime a preview deployment is created?
Is there a better way to do this? The business requirement is that some users need to have a never-changing url (staging) to see upcoming changes and then their are a few users that need to see changes (preview) that may never make it to the broader audience.
Neon branches:
- main (production)
- staging
- [preview branches]
Vercel environments:
- production
- staging
- [previews]
My idea would be to have two "static" environments (production and staging) that never change connection strings but the previews are always being created and deleted. How does that work with GitHub Actions? Does the workflow need to drop/add DB_URL environment variables anytime a preview deployment is created?
Is there a better way to do this? The business requirement is that some users need to have a never-changing url (staging) to see upcoming changes and then their are a few users that need to see changes (preview) that may never make it to the broader audience.
