3 ms·
Huge congrats for shipping some of these features. I know many of us have been wanting them for a while. In particular, migration squashing will be super helpfu
by yesimahuman 3y ago
Huge congrats for shipping some of these features. I know many of us have been wanting them for a while. In particular, migration squashing will be super helpful. I'm a little iffy on the branching stuff, since I like the solution of having two separate Supabase projects to act as different environments (though that's certainly not as powerful as actual branching, but it's simpler to reason about). Really excited to try some of the things on this list that seem new today (several of them have been out for a while as far as I can tell?)
- kiwicopple 3y ago> I like the solution of having two separate Supabase projects to act as different environments This won't be going away. Branching will just be another option fwiw, I've also heard from a few enterprise companies that the git-based branching model isn't as suitable for them, because every other tool in their stack works in a prod/stage/dev type model, and there is no simple way to make it work with (for example) ~30 different environments The branching model is really an "all-in" solution. It works particularly well if you're using something like Vercel/Netlify for your frontend. If you're using a serverside framework (Django, Rails, Phoenix, etc) then it's not as simple. That said, I think it's the way the world is moving, and with the advent of cheap VMs then it makes it very plausible even for these serverside frameworks