-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Bug]: Supabase Public schema not publicly available #2861
Comments
Interesting, I wanted to switch from Vercel to self-hosted Coolify using Supabase and Svelte-Kit for a long time now. Will probably look into the issue that you have. If possible, you can post any helpful information that is related. |
By reading what you have posted, this might be related to Supabase dashboard connection it self. I guess you are not using self-hosted Supabase? |
Interesting @mavdmichael -- have you found any workaround yet? |
I did. And it was too simple. I just put a ports: section in the docker-compose file for the db service. and that did the trick. |
Description
Brand new Supabase deploy, shows this in API docs. Same thing no matter if in Supabase Db service a port is set and marked as "Make it publicly available" or not.
Similarly, when viewing the logs in the Supabase dashboard, get a 502 error. Not sure if it's related, but guessing it is if there's an issue hitting Postgres
Minimal Reproduction (if possible, example repository)
Latest Coolify, new resource, Supabase, deploy.
Exception or Error
No response
Version
4.0.0 beta 315
The text was updated successfully, but these errors were encountered: