Hey beautiful community 馃憢
We鈥檙e on Lovable hosting + external Supabase (not Lovable Cloud). We need a clean DEV/PROD workflow.
Goals:
Questions:
I appreciate any feedback.
Thanks! Andr谩s
The user is seeking guidance on setting up a DEV/PROD workflow using Lovable hosting and external Supabase. They want to ensure separate environments for development and production, with no risk of database changes affecting production. They ask about setting environment variables per branch, creating separate projects, and handling Supabase Auth redirects.
I don't know much about supabase so i will leave 1..3 for someone else to take a look at (or maybe Lovable discord might provide good answers). On 4. There are no gotchas that i can think of, you would set redirect urls for each environment (if you can think of any specific concerns that might be more helpful) 5. Supabase branching has persistent branches which can be used for long term staging environment which when you merge in don't close. You can also use a preview branch for a long period of time. 6. Is this about producing backup storage for Supabase buckets?