-
-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realtime: Self Hosting - Docker Swarm mode #645
Comments
OK. I have made it a little farther but am still having issues. the dock-compose.yml file uses:
In order to address Realtime's use of sub-domain to determine tenants as discussed here.
To get around this I have updated my NGINX config as follows:
and my kong.yml:
It started looking for a tenant named '127' sigh, which I added to the system via the instructions here. I will figure out this later... I am now reaching the Realtime service and getting these logs:
Which is giving me a 400 error from Kong:
I am not sure what I am doing wrong in terms of the proxy pass to get a 400. Again, any help would be greatly appreciated. |
Be aware that we use the "sub domain" as a way to understand what is the tenant being accessed so I'm not sure if that nginx conf removes that information. |
@lwjameson did you ever scale past 1 node? |
@menasheh Yes I did, but the client changed strategies and went with Kubernettes instead. Docker Swarm was very tricky but it does work. |
@lwjameson How did you get the elixir nodes to connect? |
It has been a little bit, but I believe I got it to work by using a separate stack for realtime with the service named 'supabase-realtime'. Then when creating the stack I named it 'realtime-dev', and then updated the kong.yml file route for realtime to: |
@menasheh if you figured this out would love to hear, running into similar on AWS |
Thanks, this works out. I have created a service with name |
Bug report
Describe the bug
We have a project destined for open source project targeted at colleges and universities which our client requires be appropriate for self-hosting. Although the docker-compose version is fine, we really do not feel it is a viable production platform, and do not feel that a Kubernetes based solution is achievable for many institutions . I have been working on a Docker swarm implementation and am very close, with the last remaining issue being realtime.
The realtime service is driven by the following compose yaml file:
My kong.yml file is:
When our client (which works against hosted supabase) connects via wss we see the following output from the realtime logs:
The output to the kong logs 👍
To Reproduce
requires swarm setup
Expected behavior
I expect to have my websocket upgraded, but that appears to be failing
System information
Additional context
Thank you for any help you can provide here. I have been struggling with this all day.
The text was updated successfully, but these errors were encountered: