Skip to content
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

Documentation missing to use in combination with supabase for decoupled database? #477

Open
argo-uka opened this issue Jan 11, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@argo-uka
Copy link

argo-uka commented Jan 11, 2023

Improve documentation

Describe the problem

supabase/all --> the main repo which runs everything (kong, postgrest, realtime....)
supabase/postgres --> this repo

It is not quite clear how to use this repo to use it with supabase/all for decoupled postreges db. This is the most featureful Postgres docker image, yet it is quite confusing how to connect it with supabase/all. The schema migrations files doesn't work, For example, the realtime schema has become _realtime ?

I still don't know how to merge all to decouple correctly. New to docker so it is quite a journey, I'm happy to learn. But there are a lot of moving parts and it is confusing.

Describe the improvement

  • Please, provide a single docker-compose file for supabase/postgres, with the correct env vars to make it easily reachable from supabase/all compose file. In the current situation in supabase/postgres, in default branch there are 3 different docker-compose file each one ponting to different supabase/postgres. It is not quite clear which one is to run.
  • Please remove the db service in the supabase/all docker-compose file.
  • Please make the decoupled postgres the default getting started guide.

Hope to not sound arrogant.

@argo-uka argo-uka added the documentation Improvements or additions to documentation label Jan 11, 2023
@cristian-milea
Copy link

cristian-milea commented Mar 11, 2023

I find myself in the same situation. I've been struggling for 3 days now to have a decoupled Supabase db and it's very hard to follow instructions. It feels like some steps are missing and I have to come up with solutions.

If it is recommended to decouple the database, why is it so hard to configure it? :))

Love this project, but please make it easier to understand for newcomers.

@rienheuver
Copy link

I'm in this situation now as well. Trying to decouple the database and running the self-hosted Supabase, but so far no luck getting postgres up and running. Documentation on this repo is unclear to me to know how to get it running. I want to run it without Docker so my data is not gone when the machine is restart. How does this repo help me with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants