What is your Supabase workflow? - Beginner question

I'm a beginner who just started using Supabase (and postgres). I love it and for my needs, it feels like a step up from Firebase.

How do you work on Supabase with bigger projects?

• What external tools can you recommend?
• What best are the best practices when it comes to Supabase development?

So many of the articles I find are just about simple authentication or adding one function with basic row level security, but not too many dig much deeper than that.

I am finding it difficult to keep track of my functions, row level security rules etc.

Comments

[leob]

Best practice is to use a local development workflow:

supabase.com/docs/guides/cli/local...

See more details in my other comment below.

[Stefan Simic]

Absolutely agree with the need for a proper Git-based workflow! I’ve felt the same hesitation about touching the database until I leaned into Supabase CLI and their local development setup.

By spinning up a local environment, you can:

• Safely test changes without touching production.
• Generate and track migrations as code, committing them to Git.
• Apply those migrations to your live project when ready.

The workflow bridges the gap between rapid prototyping on the dashboard and professional development practices. Supabase really shines when you treat it like a database-first platform, leveraging migrations, modular SQL, and Postgres tooling.

Great tool :))

[multiply.today]

A git based workflow is sorely lacking. I find myself hesitant to touch the database because reverting changes is often a pain.

[leob]

Not true anymore apparently - there is a local development workflow:

supabase.com/docs/guides/cli/local...

You spin up a local env, and you do your migrations and all that based on code files, storing everything in Git - it's apparently even what they recommend, quote:

"Doing things directly on the platform via the Dashboard is fine when you're getting started, but it's a good idea to move to a proper local workflow before you get too far. Working locally, generating migrations as you change your tables, and applying those migrations to a linked project on the Platform keeps everything nicely organized as you grow."

The local development 'mode' does not even require a connection to the "Supabase cloud".