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

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

Open
343max opened this issue Apr 5, 2024 · 2 comments

Comments

@343max
Copy link

343max commented Apr 5, 2024

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
Copy link
Contributor

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
Copy link

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!

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

No branches or pull requests

3 participants