We’re on Lovable hosting + external Supabase (not Lovable Cloud). We need a clean DEV/PROD workflow.
We plan to create 2 lovable projects with 2 supabase instances, same git repo, different branches.
Goals: - dev branch + preview URL + stable long-term DEV database - main branch + production URL + PROD database - no risk that DB/RLS/schema changes from dev affect prod
Questions: 1) In Lovable, can env vars be set per branch (dev vs main), so each branch can point to a different Supabase project? 2) If not, is the recommended approach to create TWO Lovable projects (DEV + PROD), each connected to a different Git branch and different Supabase project? 3) For external Supabase: does Lovable ever auto-apply schema/RLS changes, or is everything only what we change inside Supabase manually? 4) Any known gotchas with Supabase Auth redirects (site URL, redirect URLs) when having dev+prod projects? 5) If using Supabase Branching: is it meant for long-term dev, or only short-lived preview environments? 6) good way to backup photos, videos, documents?
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.