Config file custom location

[parszab]

I would like to place the config.toml file in /etc but couldn't figure out how to set it for the execution -- command line parameter or env var. I really tried, checked the book and even found the newreleases.io article on the config rework but to no avail...

(Quick reference back to my previous question: I think UDS postgres would make a lot of sense, being more performant than TCP, am I really the firs one to raise it? Anyways, I'll try to create a PR, not sure when I get there.)

[sebadob]

There are basically no command line parameters, apart from some (undocumented ones) for testing, which you don't need to worry about. There is also no way to specify a custom path for the config. For the same reason as why there was not even a request for Postgres UDS so far. Rauthy is usually running inside a container, where all of this (mostly) doesn't matter.

Connecting to PG via UDS basically limits you to a single instance on a single server, which might be why no one even asked for this yet. Apart from that, the default Hiqlite is superior to Postgres in every scenario. It's (way) faster, more efficient, and way easier to operate, because you don't even need to care about updates or maintenance. The only situation where Postgres makes sense is when you already have it running anyway for something else, and you want to have the exact same backup strategy for all your databases for instance. However, if you care about the best possible performance Hiqlite is the way to go. Postgres does not even come close, and Hiqlite will run anyway for the cache.

Anyways, I'll try to create a PR, not sure when I get there.

Super simple: Add a new config variable next to pg_host called pg_socket. Parse it into the RauthyConfig just like the other values, which is a copy & paste. Then do a tiny update to the postgres connection logic in the way that if pg_socket exists, it will ignore any pg_host (and port of course) and use the UDS option.

(...) and even found the newreleases.io article.

Don't trust it. It's (probably AI) auto-generated stuff, and I have nothing to do with it.

---

I planned to add several command line options to the binary in the future for things like generating encryption keys, and so on. When this comes, adding a custom config path is pretty easy. However, this is pretty unimportant right now and I don't even know when I would start with it.

[parszab]

For the same reason as why there was not even a request for Postgres UDS so far. Rauthy is usually running inside a container, where all of this (mostly) doesn't matter.

Thank you for coming back on this, I appreciate it! I understand it now better. I myself am not a fan of the containerization of the Internet, but I know I am a minority and why others would prefer docker.

Don't trust it. It's (probably AI) auto-generated stuff, and I have nothing to do with it.

Wow, that is crazy! This slop is everywhere now!

I planned to add several command line options to the binary in the future for things like generating encryption keys, and so on. When this comes, adding a custom config path is pretty easy. However, this is pretty unimportant right now and I don't even know when I would start with it.

I'd be happy to plug in Clap with this simple example, but I guess you would have a preferred way yourself. I'll probably do it before compiling or I'll live just live with the current location till then :)

Thanks again for explaining!

[sebadob]

FYI - With the v0.35.0, you can provide a custom config file location now via

rauthy serve -c path/to/config.toml

Start the Rauthy server

Usage: rauthy serve [OPTIONS]

Options:
  -c, --config-file <CONFIG_FILE>  Provide a custom path to the config file [default: ./config.toml]
  -h, --help                       Print help