Add section summary pages and make single-link admonitions clickable

This commit is contained in:
Djeex
2026-09-04 18:51:42 +02:00
parent f2cfa49150
commit 9c5a693281
60 changed files with 451 additions and 174 deletions
@@ -193,10 +193,10 @@ Detailed info:
Once done, deploy the container.
::note
::note{to="/serveex/core/docker/#dockge"}
**Startup logs will show a temporary password for `admin` user.**
See logs in [Dockge](/serveex/core/docker/#dockge) to retrieve it, or type this command in a terminal:
See logs in **Dockge** to retrieve it, or type this command in a terminal:
```bash [Terminal]
docker logs qbittorrent 2>&1 | grep -i "temporary password"
```
@@ -224,7 +224,7 @@ When adding a download, remember to select the proper directory so Jellyfin can
::warning
Qbittorrent does not support multi-factor authentication. Exposing it to the internet may put your system at risk. Only do this if you use MFA via [TinyAuth](/serveex/security/tinyauth) or [Authentik](/serveex/advanced/authentik/). Otherwise, dont expose it with SWAG. Use a VPN like [Wireguard](/serveex/security/wireguard) instead.
Qbittorrent does not support multi-factor authentication. Exposing it to the internet may put your system at risk. Only do this if you use MFA via [TinyAuth](/serveex/security/tinyauth) or [Authentik](/serveex/advanced/authentik/). Otherwise, dont expose it with SWAG. Use a VPN like [Wireguard](/serveex/core/wireguard) instead.
::
To start downloads from outside your home, without a VPN, you can expose the Qbittorrent web UI.
@@ -267,8 +267,8 @@ We assume the network name is `seedbox_default`. You can confirm by checking the
Now create/edit `seedbox.subdomain.conf`.
::tip{icon=""}
✨ __Terminal-free tip:__ use [File Browser Quantum](/serveex/files/file-browser-quantum) to edit files instead of using the terminal.
::tip{icon="" to="/serveex/files/file-browser-quantum"}
✨ __Terminal-free tip:__ use **File Browser Quantum** to edit files instead of using the terminal.
::
```bash [Terminal]
@@ -406,9 +406,9 @@ server {
}
```
::note
::note{to="/serveex/security/tinyauth#exposing-tinyauth-with-swag"}
The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from [exposing TinyAuth itself](/serveex/security/tinyauth#exposing-tinyauth-with-swag). If you run into an error, double-check SWAG's compose file still has that network attached.
The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from **exposing TinyAuth itself**. If you run into an error, double-check SWAG's compose file still has that network attached.
::
::tip{icon=""}