`PUBLIC_DATABASE_PROXY` isn't documented anywhere, but needed for Postgres Access

teableio / teable

✨ The Next Gen Airtable Alternative: No-Code Postgres

https://teable.io

Other

11.19k stars 504 forks source link

`PUBLIC_DATABASE_PROXY` isn't documented anywhere, but needed for Postgres Access #532

Open 343max opened 5 months ago

343max commented 5 months ago

When trying to setup postgres access (yeah!) on my self hosted database I receive and error:

not_found PUBLIC_DATABASE_PROXY is not found in env

But I can't find anything what this variable should contain.

tea-artist commented 5 months ago

You need to configure the env according to the steps below: https://help.teable.io/deployment/docker-compose#starting We have fixed some errors in the previous document, The configuration for PUBLIC_DATABASE_PROXY can be found explained here: https://help.teable.io/deployment/environment-variables

Required to enable the database connection feature in Base. The public IP address or domain of the server hosting the database + the database service port exposed by Docker (default is 42345) Example: example.com:42345

mmospanenko commented 4 months ago

Will be good to not expose postgres port outside, I use traefik and one postgres for multiple services so will be great to have lightweight container (or just endpoint as proxy in main container). Anyway this project is awesome, having proxy for postgres is more than I even thought could be here, really everything what I needed (or coming soon like gantt or comments and dashboards). Thank you!