Production DB Building proccess - Moving secrets
🔢DB Connections
Hey everyone — looking for advice on migrating Edge Function
secrets between projects.
I'm setting up a production Supabase project (moving from dev) and
need to copy all my Edge Function secrets over.
supabase secrets list only shows names, not values. The management
API doesn't expose values either. And I don't have a local .env
file — I set everything directly through the dashboard/CLI at the
time.
Has anyone found a clean way to handle this? My current plan is to
manually collect each secret value from the original provider
(Stripe, Resend, 100ms, etc.) and re-enter them — but wondering if
there's a smarter approach I'm missing.
Specifically curious if anyone uses a local .env as a source of
truth from day one to avoid this problem in the future.
Thanks
secrets between projects.
I'm setting up a production Supabase project (moving from dev) and
need to copy all my Edge Function secrets over.
supabase secrets list only shows names, not values. The management
API doesn't expose values either. And I don't have a local .env
file — I set everything directly through the dashboard/CLI at the
time.
Has anyone found a clean way to handle this? My current plan is to
manually collect each secret value from the original provider
(Stripe, Resend, 100ms, etc.) and re-enter them — but wondering if
there's a smarter approach I'm missing.
Specifically curious if anyone uses a local .env as a source of
truth from day one to avoid this problem in the future.
Thanks
