From ed9158fa05f43aa3e6f33892621d8a637bbd3f9c Mon Sep 17 00:00:00 2001 From: embr Date: Tue, 21 Dec 2021 12:08:27 +0100 Subject: [fix] Make postgres connections magically work in common setups (#352) * Don't use the system 'postgres' database by default * Use postgres adapter defaults The pgx code actually goes to great lengths to make postgres connections Just Work(tm) out of the box, including supporting `~/.pg_service.conf`, SSL certificates, UNIX sockets if it can find a socket at a common path, and falling back to TCP to localhost if not. (On Windows, it won't try to use UNIX sockets, but will read credentials from %appdata% as is standard over there.) By applying our flags as overrides only when they're specified, database connections should Just Work(tm) anywhere `psql gotosocial` does. --- internal/config/defaults.go | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'internal/config') diff --git a/internal/config/defaults.go b/internal/config/defaults.go index 323e5d622..cf3e7b449 100644 --- a/internal/config/defaults.go +++ b/internal/config/defaults.go @@ -34,11 +34,11 @@ var Defaults = Values{ TrustedProxies: []string{"127.0.0.1/32"}, // localhost DbType: "postgres", - DbAddress: "localhost", + DbAddress: "", DbPort: 5432, - DbUser: "postgres", - DbPassword: "postgres", - DbDatabase: "postgres", + DbUser: "", + DbPassword: "", + DbDatabase: "gotosocial", DbTLSMode: "disable", DbTLSCACert: "", -- cgit v1.3