About testing database function
Best Practice for dev database
seed.ts
script using Snaplet, which generates a seed.sql
file that populates test data for all of my tables. This is neat, and offers a quick way to test my app locally, or even on Supabase preview branches, since I've integrated with Git and enabled automatic branching.
However, what I really want is a functional dev database that contains real data pulled from the API provider I am using. I probably won't be working with huge volumes of data, so even a clone of the production database would be fine. I've read through many posts here and seen a few people with similar use cases, but it's still pretty unclear to me what the best development pattern for this is....Cronjobs dont run

Retrive annonmous user after session clear and make session again
Unable to Sign In to Supabase Dashboard
`update().select().limit(1).single()` behavior not consistent
Race condition in insert
How to add mTLS in calling a oauth2.0 api in Edge Functions
I’m running into an issue with reCAPTCHA validation inside a Supabase Edge Function.
purchased pro last night, realized storage too expensive for my needs, canceled, asking for refund
Failed to load function code - Unknown error (URGENT)

Registered without email confirmation
Project-specific PostgREST schema cache stuck – PGRST002 errors
Set lower Maximum Duration (Wall clock limit) for edge functions
Avoid remote migrations being created when branching?
staging
branch, but every time I do Supabase runs its own migrations, even when I revert any existing ones that get added.
Screenshot is me running supabase migration list
before and after creating the staging
branch.
How can I avoid this remote migration from being created + run? What I've tried:...
[Help] Supabase Realtime stuck on joining when using multiple components in Next.js
Self-Hosted Supabase constant 100% CPU usage

Supabase MCP dont Work in my Cursor

Unexpected hard deletes happening on table (even after direct SQL inserts)
Server side auth setup help needed