permacomputing

commit 081d60005070aeed510d580c624c5bc271486baa
parent 01e1957372242880bac589d329dfc45e3a6c5159
Author: decentral1se <decentral1se@web>
Date:   Sat,  4 Apr 2026 12:27:25 +0200

fix: formatting

Diffstat:
M
eik.mdwn
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -223,7 +223,7 @@ Don't forget to `mv` it to `/usr/local/bin` and `chown rauthy:rauthy` on the bin
 
 ### 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).
+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).
 
 You can `journalctl -fu rauthy` to follow along with the logs and the usual `systemctl restart rauthy` will restart Rauthy.
 
@@ -231,7 +231,7 @@ Rauthy runs under the `rauthy` user, please prefix your commands with `sudo -su 
 
 ### 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.
+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
 
@@ -242,7 +242,7 @@ This avoids us having to hand out a HTTP basic auth username/password on top of 
 The configuration is fairly hairy but once you get it, you get it. And yes, if `rauthy` is down, there is no access. It's as solid as HTTP basic auth. The `rauthy` [docs](https://sebadob.github.io/rauthy/work/forward_auth.html#advanced-forward-auth) cover it but the TLDR; if you're moving fast:
 
 * Create a non-confidential client on Rauthy with the correct allowed origin (the URL you want to protect) and redirect URI (the URL you want to protect + /callback)
-* Disable PKCE in the Rauthy web client UI
+* Disable PKCE in the `rauthy` web client UI
 * Configure your Nginx configuration roughly like below. Refer to [the rauthy docs](https://sebadob.github.io/rauthy/work/forward_auth.html#advanced-forward-auth) for full context and tips. Please note, `<YOUR-CLIENT-ID>` must be replaced in the minimal configuration example below.
 
 Here's an example `nginx` configuration.