commit 87e6cc822b58ca18b38b5d6008d17c460dec2429
parent 961a2efa009c173e5f689d82ac9a8487bd00ab01
Author: decentral1se <cellarspoon@riseup.net>
Date: Fri, 31 Jul 2026 12:19:41 +0200
docs(eik): gardening updates
Diffstat:
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -106,7 +106,7 @@ We maintain a single patch on `bbs-patches` to disable registration (See below f
Our system configuration documentation has been upstreamed to [`docs/hosting.md`](https://github.com/cblgh/cerca/blob/main/docs/hosting.md) 🎉
-You can edit the CSS, about pages, registration instructions etc. all in `/var/www/bitrot.permacomputing.net/content/`. There are some other configurations lying around there which might be useful also. When making changes, you need to restart Cerca: `systemctl restart bbs-cerca`.
+You can edit the CSS, about pages, registration instructions etc. all in `/var/www/bbs.permacomputing.net/data/`. There are some other configurations lying around there which might be useful also. When making changes, you need to restart Cerca: `systemctl restart cerca`.
If you run into issues, have ideas for improvements or otherwise wanna get in touch with the main developer, cblgh, they're very open to discussions on the issue tracker [here](https://github.com/cblgh/cerca/issues).
@@ -128,10 +128,6 @@ You can build a static binary on your own machine with:
When there is activity on the forum we get XMPP notifications from [warawara](https://git.permacomputing.net/warawara). The binary is located at `/usr/local/bin/warawara` and if it needs to be restarted, you can `systemctl restart warawara`.
-### compost 👩🌾
-
-Our own [image uploader](https://git.vvvvvvaria.org/pmc/image_upload) for bitrot. It's deployed on eik, `systemctl status compost` to learn more.
-
motd message
------------
@@ -338,7 +334,6 @@ PAM users need to be created on the Rauthy admin side of things, connected to a
### restricting users based on group membership
-The forward authentication or group configuration on the software side ensures
-that users are members of a specific group before allowing them to log into a
-service. This allows us to have members of public participate in the forum but
-not the wiki.
+We make use of the the Rauthy feature which restricts access to specific
+clients based on group membership. This allows us to control where users with
+accounts on the SSO can log in and where they can't.
