Documentation
Edge Functions
Miglify handles Edge Functions differently depending on whether source code is available through GitHub.
Important
GitHub-backed Edge Functions can be deployed automatically because Miglify can access the source code through the connected repository. Supabase-detected-only functions require manual deployment because Supabase detection can identify the function name but cannot export source code.
GitHub-backed Edge Functions
When a repository is connected and the function's source is present, Miglify can package and deploy the function to the destination automatically.
Supabase-detected-only Edge Functions
If Miglify can only see the function through Supabase, it is detected by name but not deployed. Deploy it manually using your own source code.
Automatic deployment requirements
- Connected GitHub repository with the function's source.
- Destination Supabase project credentials.
- One-time Supabase Management Access Token for the deployment.
- Required secrets present at the destination.
Manual fallback
Deploy the function using your own tooling. Miglify continues to track secrets and readiness so the rest of the migration is unaffected.
Secrets required by functions
Configure required secrets before or after deploy. See the Secrets guide.
Testing after deployment
Invoke the function from your app or a test client to verify behavior and connectivity.
Common issues
- Missing source code in the repo — deploy manually.
- Missing secrets — configure them, then retry.
- Invalid Management Access Token — regenerate and retry.
Need beta access?
Miglify is currently in controlled private beta.