A Postgres database for every GitHub branch 🤝 GitHub branching strategy best practices

LW🆇 Day 2- Supabase Branching: supabase.com/blog/supabase-br...
Collaborative application development is super easy with tools like Git. In this video, Jon Meyers demonstrates how to use Database Branching to accomplish a similar workflow - creating an isolated PostgreSQL database for every branch in GitHub!
More Launch Week 🆇: supabase.com/launch-week?utm_...
So you want to do Database Branching using Supabase? Jon’s got you covered. In this Supabase & Postgres tutorial, Jon shows you how developers like you can manage separate database instances for each feature branch of your application, mirroring your GitHub branches and making your life as a dev MUCH easier!
What You'll Learn:
✅ Creating Separate Database Instances: Jon will show you exactly how to set up individual Supabase instances for each GitHub branch, reflecting the separation of production and feature development environments.
✅ Database Migration Management: Learn to manage database structure changes through migration files that can be tracked and committed within your GitHub repository alongside your application code.
✅ Tips & Tricks for MUCH Easier Deployment Integration: Jon will show you some hacks for automating the process of deploying database changes and integrating them into production, utilizing GitHub actions for continuous deployment. This is essential GitHub branching strategy best practices you should follow!
✅ Local and Preview Environment Testing: Obviously, you’ll need to test! Learn how to test new database functionalities in isolated environments before merging them into the main branch, ensuring robust, error-free app releases and roll-outs. Again, a perfect GitHub branching strategy for multiple environments you should watch!
Why You Should Care About This Postgres Database for Every GitHub Branch Video:
Database branching simplifies managing database versions across different stages of development, ensuring each feature has an isolated environment. By doing this, you’re reducing conflicts and keeping your application and database schema perfectly aligned without disrupting the main production environment.
You’ll also learn:
✅ Setting up a new feature using Supabase’s branching capabilities.
✅ Adding and managing new database columns through Supabase Studio.
✅ Automating deployments and database migrations with GitHub actions.
✅ GitHub branching strategy best practices
This is your guide to making the most of database branching to ensure consistent, error-free deployments. Perfect for developers using Supabase and GitHub! We hope this video helped some dev’s out there!
💻 Videos to watch next:
▶ Watch all Postgres Supabase videos: • Learn Postgres
▶ Postgres...but JSON? • How to store and query...
▶ This is why you MUST be using Postgres functions and transactions: • 3 reasons you should u...
👇 Learn more about Supabase 👇
🕸 Website: supabase.com/
🏁 Get started: app.supabase.com/
📄 Docs: supabase.com/docs
🔔 Subscribe for more tutorials and feature updates from Supabase: / @supabase
📱 Connect with Us:
🐙 Github: www.github.com/supabase
💬 Discord: www.discord.supabase.com/
🐦 Twitter: / supabase
▶ Instagram (follow for memes): / supabasecom
ABOUT SUPABASE:
Supabase is the open source Firebase alternative. Supabase provides a full Postgres database for every project with pgvector, backups, realtime, and more. Add and manage email and password, passwordless, OAuth, and mobile logins to your project through a suite of identity providers and APIs.
Build in a weekend, scale to millions.
#Supabase #AppDevelopment #RealtimeApps #DeveloperTools

[@Supabase]

Keep up with everything we are launching here: supabase.com/launch-week?

[@antonkouliavtsev2501]

Awesome! I was really looking forward to this one. :)

[@JonMeyers]

Yeah, I am so excited! It also unlocks some pretty amazing things for the future! of Supabase! 🚀

[@thorwebdev]

The GitHub for Postgres, amazing work! 💪

[@dshukertjr]

This is what everyone has been waiting for!

[@eez]

this is awesome... game changer ..thanks for the demo.

[@JonMeyers]

Absolute game changer! Glad you enjoyed it! 🙌

[@maloxi1472]

I'd love to see this kind of integration with Cloudflare Pages 😲

[@JonMeyers]

That would be awesome! 💯

[@JonMeyers]

Branches can still be created manually. The Vercel integration just automates the process! 🚀

[@dnlmgwi]

Supabase!

[@JonMeyers]

This is only the beginning! 🚀

[@Supabase]

🫡

[@jeremytenjo]

wow

[@JonMeyers]

I know, right?

[@nikhilpsathyanathan]

This is cool. What happens if there is a migration error?

[@StefanRows]

You should have mentioned that Database Branching is only available on the Pro Plan :)

[@caseyspaulding]

Holy S***! Awesome. Thank you.

[@supa_olirice]

this is awesome 🚀

[@AnindoSarker]

exactly what I was looking for.

[@rodrigomansuelinunes1285]

Let's branch it out!

[@kamil_supabase_enjoyer]

Good but who creates features right from the PRODUCTION branch? Can you show us normal workflow like DEV, QA, PROD?

[@bnssoftware3292]

Would be really helpful if you did a tutorial on how to build a Dashboard and Customer management portal similar to what you see in Supabase.

[@frnk_snslvdr]

so cool 🤯🤯🤯

[@cheapliquor4530]

This is great! Does this feature also covers changes to Edge Functions, or only to the Database?

[@kamil_supabase_enjoyer]

Great. I wonder how it can work with mobile apps especially Flutter.

[@awalias]

can't wait to spin up 100000000x branches

[@ShadowsPowerFy]

Is it posibble to use this without running supabase locally? So i dident have to make migrations.

[@ThomasSselate]

Vercel creates preview links for commits, branches, PRs... Will all these work ? What if there are no new migrations, will it create a branch anyway, or connect to the main one ? Does the branch live as long as the Vercel preview ?

[@holycrimpsauce]

It’s a cool feature. But I don’t want to use Vercel personally. And work uses AWS.

[@JonathanSummersMuir]

Nice! How are you using AWS today?

[@JonMeyers]

Branches can be created manually - the Vercel integration just automates the process! 👍

[@dave_m98]

How do I make a .supabase folder? Is it like all my supabase configurations I looked online but couldn't find anything. Great video, by the way!

[@JonathanSummersMuir]

Have you been using the CLI to make migrations already?
if so, you probably already ran `supabase init` which means you already have a ./supabase directory in your repo. Branching will use the same directory and the same migration files. Also your seed.sql file will work as well.

[@amiranvarov]

so it is same thing that Prisma was offering in their migrations?

[@peteredmonds1712]

How about Supabase Functions? Could I set up a new endpoint, perhaps a postgres trigger, and have it deployed in a preview env?

[@Supabase]

Yup, as long as you include the function definition in the migration file, it will be available in the preview branch!

[@peteredmonds1712]

@@Supabase Hmm okay. Will that newly added edge function (or any changes to existing functions) also modify my production environment, or are function changes local to that preview environment? If so, how does supabase resolve endpoints in different preview environments?

[@davebenjamin4388]

when do you expect this to come out of alpha? there's currently a warning in your docs not to use this for production systems...

[@DeepakDonde]

It would be great if you slow down a little bit....