Expose the DB port to the host machine so it's easy to use tools like TablePlus #85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, There is an open issue for this at: #42 I'm on the fence about it based on the comments in that thread but thank you for the contribution. |
|
I see, but allowing connections only from the host machine should be a safe choice, no? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During development, it's very convenient to connect to the database using tools like TablePlus. I think these tools are very helpful for developers to quickly get feedback on the data they're working with.
I guess it's better to go for a non-default postgres port in order to avoid issues if the developer already has postgres running through brew services.