permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit e225b7e49b5c2e490f7d65e267b6fc884a5bb6bf
parent 0a5248e3f74090a06105549d379901dc8dee65e6
Author: decentral1se <decentral1se@web>
Date:   Sat,  4 Apr 2026 21:11:04 +0200

chore: convention

Diffstat:
Meik.mdwn | 10+++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/eik.mdwn b/eik.mdwn @@ -202,10 +202,10 @@ We seem to be doing this. And then using these in `systemd` files to run services with users with limited permissions. This is at least the case for `cerca` and `rauthy`. Documenting this in case we choose to do it differently in the future. -Rauthy +rauthy ------ -### Build +### build Install [rustup](https://rustup.rs), grab `musl-tools` and a copy of the Rauthy source code. You'll need to follow [the standard contrib docs](https://github.com/sebadob/rauthy/blob/main/CONTRIBUTING.md) to get a working development environment up and running. @@ -221,7 +221,7 @@ You can transfer to eik like so. Don't forget to `mv` it to `/usr/local/bin` and `chown rauthy:rauthy` on the binary. You should also make sure `rauthy` is stopped on eik before replacing the binary. -### Configure +### configure The `rauthy` binary lives in `/usr/local/bin/rauthy` and it's configuration and data is to be found in `/etc/rauthy/config.toml`. Here are the [configuration reference docs](https://sebadob.github.io/rauthy/config/config.html). @@ -229,11 +229,11 @@ You can `journalctl -fu rauthy` to follow along with the logs and the usual `sys Rauthy runs under the `rauthy` user, please prefix your commands with `sudo -su rauthy` if running commands directly on the configuration or data to avoid borking permissions. -### Admin +### admin See the `config.toml` for the fallback admin email. Ask in Toolshed for the password. You can also create an account and be upgraded to administrator by applying the `rauthy_admin` role on user creation. -### Arbitrary single sign-on +### arbitrary single sign-on It is possible to configure `nginx` to use the [`forward auth`](https://sebadob.github.io/rauthy/work/forward_auth.html#advanced-forward-auth) feature of `rauthy`. This means, you can put anything you serve on `nginx` behind a single sign-on.