Support custom pg-meta, studio, pooler, and realtime images

[S96EA]

Is your feature request related to a problem? Please describe. I built a custom postgres-meta image, and I want to start it using cli command, like supabase start, but now the image is written in code.

Describe the solution you'd like Cloud we put the image written in code to config file, like db image.

[sweatybridge]

We can consider reading the pg-meta version from a temporary file, like supabase/.temp/pgmeta-version. We do the same for db, auth, and other images when user links their local project to a hosted project.

We probably don't want to add a config field because it will be difficulty to guarantee newer versions of studio and cli will work the every old version of pgmeta. We don't need to worry about backwards compatibility for temporary files since they are not committed to git and may be deleted anytime.

[S96EA]

It looks like we can't reach online pgmeta api, when I called https://my-project-xxx.supabase.co/pg/, the API returned no Route matched, but when I called a local api endpoint http://127.0.0.1:54321/pg/, it returned the right output: {"status":200,"name":"@supabase/postgres-meta","version":"0.0.0-automated","documentation":"https://github.com/supabase/postgres-meta"}.

[sweatybridge]

It looks like we can't reach online pgmeta api

You are right. It's not open to public directly but some of our platform api routes proxy to pgmeta, like typegen. It will be useful to figure out a way for contributors to test pgmeta.

Could you elaborate on the changes you plan to make to pgmeta? Perhaps there's an alternative way to test it.

[S96EA]

I noticed that there is an API in pgmeta that provides the version, I'm wondering if it's possible to read the pgmeta through this API, like we do with GoTrue. Then we can save the version of pgmeta in a temporary file.