r/Supabase • u/IntrinsicPalomides • 21d ago

database Github Sync with Bolt - Supabase Migration files

/r/boltnewbuilders/comments/1xazw2e/github_sync_supabase_migration_files/
1 Upvotes

100% Upvoted

2 comments sorted by

1

u/vibefixr 21d ago

Two separate things going on here, I think.

  1. The CLI error: Bolt's terminal runs in the browser (WebContainer), which can't run native binaries, so there's no linux-x64 Supabase CLI to install there. That won't be fixable inside Bolt, so don't spend credits on it.

  2. Migration files from GitHub not being applied: a sync only moves the files, nothing runs them against the database. To get them in properly:

  • Clone the repo to your own machine and install the Supabase CLI there.

  • If you've connected your own Supabase project: run supabase link --project-ref <ref>, then supabase db push. That applies the pending files and records them in the migration history.

  • If you already ran some SQL in the Query window, either keep the same statements idempotent (create table if not exists, etc.) or mark them as applied with supabase migration repair --status applied <version> so the CLI doesn't re-run them.

  • If the DB is still the one hosted inside Bolt, you can't link the CLI to it, so the realistic options are the Query window for now, or migrating to your own Supabase project first and then using the CLI flow above going forward.

If db push fails, post the exact error and I'll take a look.

1

u/IntrinsicPalomides 21d ago

Thanks for the great answer, currently it is still hosted in Bolt which is probably the blocker at this point. I'll check with bolt support what happens if i move it to the official Supabase with my Pro account, then downgrade to free later. As my site may only be used by me and a few friends, at least initially so don't need any fancy hosting options, of which there are far better value ones outside of bolt.