Han Qiao

possibly related https://github.com/supabase/cli/issues/2288

> Bounty expired. I was able to build the image by removing the final stage of the Dockerfile (Remove all lines after HEALTHCHECK ...) No need to delete anything. You...

For backwards compatibility, you need to add a new config block for mailpit. But even then, I don't think this change is necessary because the ports 1025 and 1110 are...

> This does not work since the docker running the shadow database is created on host, and 127.0.0.1 for host network is not accessible from inside our container. The shadow...

It's because we updated postgres to [15.8.1.060](https://github.com/supabase/cli/pull/3348) which removed the pgsodium schema by default. As mentioned in the error message, the statement 11 of your `supabase/migrations/20241104023930_init_dump.sql` file is creating the...

> Will this be fixed in any package/dependency or will deleting the line stay as the only option? It's more complicated in this case because we plan to sunset the...

> isn't the vault using pgsodium by default? Yes, it is at the moment, but it's an implementation detail of vault that we plan to change. When you install vault...

> Now I can of course comment out this line locally and even drop this extension in prod, but then my dev and prod migrations will diverge. Just to clarify,...

> How will the upgrade work? We're pretty dependent on pgsodium at the moment, using it for dispatching webhooks [with standard webhook signatures](https://github.com/orgs/supabase/discussions/14115#discussioncomment-10624338) like how [the custom auth hook does...

> However I can still see CREATE EXTENSION IF NOT EXISTS "pgsodium" WITH SCHEMA "pgsodium" in my first db migration if I go to the Database Migrations page in Supabase,...