Different migrations per env

Hi, I'm trying to setup webhooks via a migration file - let's take the documentation example

create trigger "my_webhook" after insert
on "public"."my_table" for each row
execute function "supabase_functions"."http_request"(
  'http://host.docker.internal:3000',
  'POST',
  '{"Content-Type":"application/json"}',
  '{}',
  '1000'
);

create trigger "my_webhook" after insert
on "public"."my_table" for each row
execute function "supabase_functions"."http_request"(
  'http://host.docker.internal:3000',
  'POST',
  '{"Content-Type":"application/json"}',
  '{}',
  '1000'
);

I'd like the migrations on local dev machines to point to local server, but once in production I want it to point to my prod server - is there a way to do this ?

Supabase•9mo ago•

2 replies

Ninjeneer

Different migrations per env

Hi, I'm trying to setup webhooks via a migration file - let's take the documentation example

create trigger "my_webhook" after insert
on "public"."my_table" for each row
execute function "supabase_functions"."http_request"(
  'http://host.docker.internal:3000',
  'POST',
  '{"Content-Type":"application/json"}',
  '{}',
  '1000'
);

create trigger "my_webhook" after insert
on "public"."my_table" for each row
execute function "supabase_functions"."http_request"(
  'http://host.docker.internal:3000',
  'POST',
  '{"Content-Type":"application/json"}',
  '{}',
  '1000'
);

I'd like the migrations on local dev machines to point to local server, but once in production I want it to point to my prod server - is there a way to do this ?

Different migrations per env

Similar Threads

Different migrations per env

Similar Threads

Similar Threads

Similar Threads