Fix postgres connection issue and typo in postgres readme #83
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
Merged
korikuzma
approved these changes
Feb 21, 2024
theferrit32
force-pushed
the
fmt-and-docs-fixes
branch
from
0972adf to
f22652f
Compare
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.
If you follow the postgres instructions in our docs you will now get a connection issue, with the postgres server rejecting the connection for not having a password.
This PR fixes this issue by updating the postgres user to have a password, and including that password in the connection string.
And includes a typo fix for
README-pg.mdDepends on #82