Self-hosting on Azure

[mellson]

Is it possible to self host Supabase on Azure? I've stumbled upon a "small" roadblock in the form of pgjwt not being available in Azure Database for PostgreSQL. Has anyone tried to self-host on Azure and found a way around this problem?

[jordevorstenbosch]

I've been trying as well, and the only way to get it to work is to basically host the DB yourself (even if on a separate machine).

Documentation is misleading as it initially says:

Using an external database
We strongly recommend that you decouple your database from docker-compose before deploying. The middleware will run with any PostgreSQL database that has logical replication enabled. The following environment variables should be updated in the .env file to point to your external database:

As well as:

It is recommended that you decouple your database from the middleware so that you can upgrade the middleware without any downtime. The "middleware" is everything except Postgres, and it should work with any Postgres provider (such as AWS RDS), or your own Postgres cluster.

But in reality it indeed requires pgjwt as well as superuser and bypassrls which no major cloud provider seems to support.

Even the mentioned AWS RDS does not support pgjwt if I'm to believe their documentation:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.Extensions.Trusted=

I've only used DO and Azure personally, and I can't get supabase self-hosted to run with their managed DBs. So I guess we're stuck with IaaS for those scenarios.

[ElToro13]

Same issue here. pyjwt doesnt work even with AWS RDS. Their Documentation says AWS RDS is fully supported. But when you run their extensions creation commands, all works expect

create extension if not exists pgjwt with schema extensions;

[steve-chavez]

Note that pgjwt is pure SQL, you can create it without doing create extension. Some instructions here.

[jordevorstenbosch]

Even when you add pgjwt manually it still won’t run without all the extra permissions it requires.

[ElToro13]

Also like to add that Self hosting is not working for me with AWS RDS
Can't connect to supabase-auth

supabase-auth | time="2022-07-15T14:09:51Z" level=fatal msg="running db migrations: Migrator: problem creating schema migrations: CREATE TABLE \"schema_migrations\" (\n\"version\" VARCHAR (14) NOT NULL\n);\nCREATE UNIQUE INDEX \"schema_migrations_version_idx\" ON \"schema_migrations\" (version);: ERROR: no schema has been selected to create in (SQLSTATE 3F000)"
supabase-auth | [POP] 2022/07/15 14:09:51 info - 2.6074 seconds
supabase-auth exited with code 1

[ElToro13]

No.. had to rewrite my entire backend code

[PrasannaSM]

backend as in supabase auth image?

[ElToro13]

no. Removed supabase altogether and use Postgres directly

[PrasannaSM]

@ElToro13 Thats good. So, let me tell you my use case. The thing to vendor lock I am looking for an alternate to firebase realtime database [for live sync]. I stumbled upon supabase as an interim solution. I wanted to try out self-hosted supabase with AWS RDS. Now, facing with this error. Any suggestions

[ElToro13]

this was my first project with SQL. I usually worked with NoSQL (MongoDB). So really didnt know much about how to fix this error. I wrote a Stackover flow question regarding the same. Someone was kind enough to write a detailed answer. You can check it out here. Hope that helps!

[AnkityadavIITR]

can anyone help to deploy supabase on azure container apps