Configure External PostgreSQL for Supabase Instead of supabase-db

[Bayireddy-Sai]

I am trying to configure Supabase to use an external PostgreSQL database instead of the default supabase-db (the internal PostgreSQL instance managed by Supabase).

Currently, Supabase uses an internal PostgreSQL database (supabase-db), but I need to connect it to an externally managed PostgreSQL instance for better scalability and control.

Changes I Have Made:

I have set up an external PostgreSQL instance and created a new database (supabase_db) with the necessary Supabase-related roles (supabase_admin, authenticator, anon, service_role, etc.).
I updated the docker-compose.yml file to replace supabase-db with my external database connection string:
environment:
DB_URI: "postgresql://supabase_admin:your_password@your_external_host:5432/supabase_db"

after updating db, I facing an issue with schema migrations

1. Is there an official guide or best practice for using an external PostgreSQL database with Supabase?
2. Are there any additional configurations needed to fully migrate all Supabase services (Auth, Storage, Realtime, PostgREST, etc.) to an
   external database?
3. Does Supabase expect specific schemas, roles, or privileges that should be manually assigned when using an external PostgreSQL
   instance?
4. Are there any known compatibility issues or performance considerations when using an external database?

[samikrc]

Have you seen this article: https://dev.to/arthurkay/self-hosted-supabase-with-external-postgresql-apd
Haven't done this myself yet - but this article seems popular.