feat(redis): Support using Unix socket

[shivaraj-bh]

resolves #352

[niklasmohrin]

Thanks!

I wonder if it would be worth it to unify the option names around sockets. Right now, process-compose-flake has httpServer.uds = "path-relative-to-project-root", redis has unixSocket = "path-relative-to-data-dir" and postgres has socketDir = "path-relative-to-project-root" (with no way to specify the name, but just the directory; I think it's okay though). One annoyance with the process-compose uds option is that using "data/process-compose.socket" won't automatically create the data/ directory and instead fail.

[shivaraj-bh]

Thanks!

I wonder if it would be worth it to unify the option names around sockets. Right now, process-compose-flake has httpServer.uds = "path-relative-to-project-root", redis has unixSocket = "path-relative-to-data-dir" and postgres has socketDir = "path-relative-to-project-root" (with no way to specify the name, but just the directory; I think it's okay though). One annoyance with the process-compose uds option is that using "data/process-compose.socket" won't automatically create the data/ directory and instead fail.

Usually we try to match what’s upstream so users coming from there don’t have a hard time figuring out options. For redis it is the same as in nixos module in nixpkgs. nixpkgs doesn’t define an option to configure socket dir for postgres, so we can consider renaming that for uniformity. Even uds in process-compose-flake can be re-considered.

[niklasmohrin]

Usually we try to match what’s upstream so users coming from there don’t have a hard time figuring out options. For redis it is the same as in nixos module in nixpkgs

Ah, yeah, that makes perfect sense!

nixpkgs doesn’t define an option to configure socket dir for postgres, so we can consider renaming that for uniformity. Even uds in process-compose-flake can be re-considered.

I am not sure what the postgres config file instruction for this is called, but I guess using this would make sense. Maybe this even is socketDir. Process compose seems to be a bit messy as the CLI flags are --use-uds and --unix-socket but the environment variable for the latter is PC_SOCKET_PATH.

---

Overall, I don't really mind, all options are somewhat okay to find. Since different programs have different ways of offering the same functionality, some heterogeneity in the naming here is probably unavoidable. I suppose finding a unified way that intuitively makes sense is not as easy as I initially made it out to be. Good documentation can probably make any naming scheme work