[fix] Make postgres connections magically work in common setups #352
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.
First of all, this changes the default database name to
gotosocial
; dumping our tables into the systempostgres
table probably shouldn't be the default.Second, I started reading the
pgx
code, and it actually goes to great lengths to make postgres connections work out of the box:~/.pg_service.conf
and TLS client certificates in standard paths.localhost
.Which means that if we just unset our default credentials, and apply them only if actually set in our config, the database connection should Just Work(tm) anywhere
psql gotosocial
would.https://github.com/jackc/pgconn/blob/a123e5b4e575b5eb3c68ae4ab87c508d341242df/defaults.go
https://github.com/jackc/pgconn/blob/a123e5b4e575b5eb3c68ae4ab87c508d341242df/defaults_windows.go