Technical post-mortem of renaming a production Lovable app. What broke: stale URLs in 47 files, Supabase table references, Stripe product mappings, Cloudflare DNS cutover, Sentry project rename. The grep-across-second-brain pattern that should have run at rename time. Lessons for any indie builder doing a rebrand.
Chad Dyar
Posted on
From PillPal to CareCadence: A Live Rebrand Across 47 Files and 4 Database Tables
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
Table renames on a live Supabase project make me nervous, mostly about whether RLS policies survive intact. When you did the renames, did a straight ALTER TABLE RENAME carry the policies over automatically, or did some need to be rebuilt by hand afterward?
RLS policies attach to the table OID, not the name, so a plain ALTER TABLE RENAME carries them over automatically -- nothing to rebuild by hand there. Where it does bite is if the old table name is baked into a string literal inside dynamic SQL (EXECUTE) -- those don't follow the rename and have to be hunted down manually. Did you run into any of those, or was the rename itself the main risk you were watching for?