-
Notifications
You must be signed in to change notification settings - Fork 9
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
How to expose postgresql container to public? #10
Comments
Well this change was by design, I want to be able to run a PG server on the host while running this plugin side by side. Now what you’re asking is doable, you’ll have to add I could also add an option to bind the container externally while keeping the default behavior of not binding externally. |
Thank you for the solution, it will work! |
Yes, you’re right, I’m taking a look ;) |
Done! Available in the latest master (instructions in README) 😁 |
Sorry for bothering you again, lot of "dockerizing" lately :) Now for one app i have another wish related to this one, i would like to bind container not to I wish you implemented something like Would you consider this as a feature? |
What do you think? |
I think |
I think I will still add this feature ;) |
Replace `PSQL_SC_BIND_EXTERNAL` with `PSQL_SC_BIND_IP`. See README for instructions. Closes #10
Done in latest master 😄 |
Currently i see that
5432/tcp
port is exposed for local connections.But i guess i need to bind it to exactly
0.0.0.0:5432->5432/tcp
in order to make postgresql listen public.When i was using original
ohardy/dokku-psql
repo the exposed ports looked like this:Could you please help me what do i need to change to make my postgresql container to be available in public? Is it somehow configurable?
Thanks.
The text was updated successfully, but these errors were encountered: