unlovable provides a small helper for bootstrapping local Supabase development in a Lovable project.
The main command is unlovable-local-supabase and lovable-local-supabase remains available as a compatibility alias. Both names run the same bootstrap flow, which:
- detects the current Lovable git repo
- ensures Docker is running
- auto-installs the Supabase CLI if it is missing
- rewrites
.env.localto point the app at local Supabase - updates
supabase/config.tomlto a deterministic local project id - starts local Supabase if needed
- applies pending local migrations without resetting by default
- supports an explicit reset flow when needed
- creates
docs/supabase-status.mdif it does not already exist
make installThis installs the command into ~/.local/bin and ensures ~/.zshrc includes that path.
unlovable-local-supabaseUseful variants:
unlovable-local-supabase --skip-start
unlovable-local-supabase --reset
unlovable-local-supabase --reset --no-seed
unlovable-local-supabase --project-root ~/code/my-lovable-appCompatibility alias:
lovable-local-supabaseUse this when your Lovable app lives in a separate repo, such as
/Users/jmfk/code/monster-meadows.
make install
unlovable-local-supabase --project-root /Users/jmfk/code/monster-meadows
cd /Users/jmfk/code/monster-meadows
npm i
npm run devWhat happens:
unlovable-local-supabasestarts local Supabase for the target app repo- it writes
.env.localin that repo with the local Supabase URL and keys - it updates
supabase/config.tomlto a deterministic local project id - it creates
docs/supabase-status.mdif that file does not already exist - after that,
npm run devstarts the app against the local Supabase instance
- default reruns are idempotent and preserve the existing local database state
- the repo is wired to local Supabase through
.env.local supabase/config.tomlis kept aligned with the local project id- pending migrations are applied with
supabase db push --local --resetperforms a clean rebuild of the local database
USAGE.mdfor installation and command detailsdocs/local-supabase.mdfor local dev notes and self-hosted migration guidancedocs/supabase-status.mdfor generated local runtime status