Topic

Edge Functions

1 post about Edge Functions. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Supabase
How a new branch gets its config, migrations, and functions
Supabase branches are independent projects that require settings, schema, and edge functions to be set up before use. When a branch is created, configuration copies main project settings including Postgres, Auth, and Realtime config, then applies them with a single Postgres restart via walg_enable; Auth secrets do not carry over. Migrations come from the git repo for GitHub-connected branches or from the main project’s migration history for gitless branches; each file runs as one transaction in pipeline mode. Edge functions are copied from the main project at creation in parallel with configuration, and on each push only changed functions are redeployed using Brotli compression and SHA-256 checksums. If a step fails, it shows as DEAD and stops dependent steps, while PAUSED indicates a warning that does not block subsequent steps.

The best engineering reads, once a week.

Topic

1 post about Edge Functions. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Supabase
How a new branch gets its config, migrations, and functions
Supabase branches are independent projects that require settings, schema, and edge functions to be set up before use. When a branch is created, configuration copies main project settings including Postgres, Auth, and Realtime config, then applies them with a single Postgres restart via walg_enable; Auth secrets do not carry over. Migrations come from the git repo for GitHub-connected branches or from the main project’s migration history for gitless branches; each file runs as one transaction in pipeline mode. Edge functions are copied from the main project at creation in parallel with configuration, and on each push only changed functions are redeployed using Brotli compression and SHA-256 checksums. If a step fails, it shows as DEAD and stops dependent steps, while PAUSED indicates a warning that does not block subsequent steps.

The best engineering reads, once a week.