Realtime Tenant Issues
Hi,
I’m trying to get Realtime working on a self-hosted Supabase setup. I deployed Supabase using the Dokploy template, but we’ve already customized a lot of things. So far, I haven’t been able to make Realtime work.
I’ll share part of our configuration below.
The main issue is that our setup doesn’t allow Kong to resolve URLs like
With this configuration, the system can communicate with the Realtime container, but it tries to use a tenant named
My question is: How can I configure it so that the tenant is correctly passed and it uses
Thanks in advance!
I’m trying to get Realtime working on a self-hosted Supabase setup. I deployed Supabase using the Dokploy template, but we’ve already customized a lot of things. So far, I haven’t been able to make Realtime work.
I’ll share part of our configuration below.
The main issue is that our setup doesn’t allow Kong to resolve URLs like
http://[tenant].realtime:4000, because it doesn’t recognize the [tenant] part. The only URL that works is http://realtime:4000.With this configuration, the system can communicate with the Realtime container, but it tries to use a tenant named
"realtime" instead of "realtime_dev" since the tenant is not defined.My question is: How can I configure it so that the tenant is correctly passed and it uses
"realtime_dev"? Or would it be better to simply create a new tenant named "realtime"?Thanks in advance!
