Using already available (remote) postgres instance?

[tmplt]

Hey @kiriwalawren, would it be in-scope for nixflix to be able to use an already existing non-local postgres instance? I already have one for immich, forgejo, etc, and would prefer a single instance (streamlined ops, backups, infra). I could probably override the nixflix defaults, but I figure it would be better to natively support it in the nixflix options set.

Or is this negative for performance? I'm mostly thinking in terms of centralizing data storage here (pgres is on my NAS where all the media/downloads also are; 3-2-1 backup has been made trivial with snaphot replication this way).

[kiriwalawren]

I agree. This is probably in-scope. The settings should be defined at nixflix.postgres.users = [{ name = "sonarr"; password._secret = "/some/path"; databases = ["database1" "database2"] }] level. Then, each service can "register" itself with the postgres integration, which actually has central control, based on the nixflix.postgres.enable option.

To note, all of these services rely on unix authentication, and databases named after the user, effectively passwordless. So, it is going to be a bit of a lift.