caelum0x 261ea5dea7 feat: scribase-migrate — one-command migration from Supabase/Neon/Clerk/Resend onto Scribase
Composes Scribase's own shipped APIs (the `scribase` SDK's imports/migrations/
database/environments resources, plus the GoTrue admin API every self-hosted
Supabase migration tool already uses) rather than reinventing a dump format:

- supabase: wraps the real POST /v1/imports one-call migration (Postgres,
  auth.users with hashes, storage).
- neon: pg_dump schema+data as plain SQL, submitted through POST .../migrations
  (environments.connection() is internal-network-only — verified live — so
  this is the only path that actually reaches a Scribase env from outside);
  auto-generates owner-based RLS so the real migration lint's BLOCK on
  RLS-less public tables is satisfied without ever opening a table to every
  user; branches land in branch_<name> schemas.
- clerk: exports users via the real Backend API, creates them via the
  destination's GoTrue admin API with a one-time password + reset flag
  (Clerk never exposes a portable hash on any plan).
- resend: exports sending domains + broadcasts (as templates) to a portable
  JSON bundle; honest about Scribase having no write endpoint for either yet.

Verified live end-to-end against a real local Supabase-shaped Postgres
(Docker, GoTrue-shaped auth.users with a real bcrypt hash) and a real
Scribase project (ereboslab/scribase-migrate-verify-internal): schema+RLS
applied with 0 lint blocks, data row counts matched via a real HTTP query
(2/2 profiles, 3/3 notes), and a real password-grant login returned a real
access_token for the migrated user. Full artifacts in
test-fixtures/verification-run/.

docs/migrate-page.md is a ready-to-paste scribase.com/migrate page.
2026-11-17 14:54:36 +03:00

43 lines
1.6 KiB
JavaScript

/**
* Supabase -> Scribase: the one real API call. Scribase's control plane
* already has a native `POST /v1/imports` path for `source: 'supabase'`
* that connects to the source project itself (Postgres schema + data,
* `auth.users` with password hashes intact, and storage buckets+objects)
* and reports per-table row/checksum parity plus an optional live login
* proof. This module is a thin, validated wrapper around the official
* `scribase` SDK's `client.imports` resource — composing the existing,
* already-shipped migration engine rather than re-implementing it.
*/
/**
* @param {import('scribase').ScribaseClient} client
* @param {{
* sourceProjectRef: string,
* sourceConnectionString: string,
* sourceServiceKey: string,
* destination: { organizationId: string, projectId: string, environmentId: string },
* includeStorage?: boolean,
* verifyLogin?: { email: string, password?: string },
* dryRun?: boolean,
* onProgress?: (job: unknown) => void,
* }} opts
*/
export async function migrateSupabase(client, opts) {
const request = {
source: 'supabase',
sourceProjectRef: opts.sourceProjectRef,
sourceConnectionString: opts.sourceConnectionString,
sourceServiceKey: opts.sourceServiceKey,
destination: opts.destination,
includeStorage: opts.includeStorage ?? true,
...(opts.verifyLogin ? { verifyLogin: opts.verifyLogin } : {}),
};
if (opts.dryRun) {
return { kind: 'dry-run', plan: await client.imports.dryRunFrom(request) };
}
const report = await client.imports.run(request, opts.onProgress ? { onProgress: opts.onProgress } : {});
return { kind: 'report', report };
}