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.
Top comments (3)
A git based workflow is sorely lacking. I find myself hesitant to touch the database because reverting changes is often a pain.
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".
Best practice is to use a local development workflow:
supabase.com/docs/guides/cli/local...
See more details in my other comment below.