Djeex/docudjeex
1
1
Fork 0
Code Issues Pull Requests Actions Projects Wiki Activity

Fix Done! spacing site-wide, and EN-only content errors (Docker/Linux mixup, missing spaces, ProloNAS pun explanation)

Browse Source
This commit is contained in:
Djeex
2026-09-07 13:49:44 +02:00
parent fbc33a5ff4
commit 328aa31600
38 changed files with 116 additions and 116 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/3.serveex/4.monitoring/1.uptime-kuma.md
+3 -3
View File
@@ -62,7 +62,7 @@ You can now access the tool via `http://yourserverip:3200`.
__If it fails:__ check your firewall rules.
::
### Done !
### Done!
::
## Expose with Swag
@@ -173,7 +173,7 @@ Restart the stack and wait until SWAG is fully operational.
Here we assume that the network name of Uptime-Kuma is `uptime-kuma_default`. You can verify the connection by visiting SWAG's dashboard at `http://yourserverip:81`.
::
### Done !
### Done!
::
That's it! Uptime-Kuma is now exposed, and you can access it via `https://stats.mydomain.com`.
@@ -245,7 +245,7 @@ The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs t
Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
### Done !
### Done!
::
Redeploy the stack. Uptime-Kuma will then be publicly reachable via `https://stats.mydomain.com`, with the status page open and everything else behind TinyAuth.
content/en/3.serveex/4.monitoring/2.dozzle.md
+2 -2
View File
@@ -101,7 +101,7 @@ DOMAIN=dozzle.mydomain.com
Deploy the container. Go to `http://yourserverip:9135`. Voilà, your Dozzle web UI is up and running!
### Done !
### Done!
::
## Exposing Dozzle with Swag
@@ -214,7 +214,7 @@ server {
Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
### Done !
### Done!
::
And there you go, Dozzle is now exposed!
content/en/3.serveex/4.monitoring/3.speedtest-tracker.md
+2 -2
View File
@@ -89,7 +89,7 @@ PORT=3225 # port to access the web UI
Deploy the container and go to `http://yourserverip:3225`. Log in with the account `admin@exemple.com` and the password `password`. Don’t forget to change your ID and password once logged in!
### Done !
### Done!
::
## Exposing Speedtest Tracker with SWAG
@@ -194,7 +194,7 @@ Restart the stack by clicking "Deploy" and wait for SWAG to be fully up.
This assumes the Speedtest Tracker network is named `speedtest-tracker_default`. You can verify the connection by visiting SWAG’s dashboard at `http://yourserverip:81`.
::
### Done !
### Done!
::
Wait a moment, then visit `https://speedtest.yourdomain.com` in your browser. You should be redirected to Speedtest Tracker. You can check service status via the dashboard (`http://yourserverip:81` from the local network).
content/en/3.serveex/4.monitoring/4.beszel.md
+2 -2
View File
@@ -108,7 +108,7 @@ For the `KEY` value, you'll need to launch Beszel once to get it.
Deploy the container and go to `http://yourserverip:8090`. Your Beszel web UI is now accessible!
### Done !
### Done!
::
::caution
@@ -286,7 +286,7 @@ server {
Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
### Done !
### Done!
::
That’s it! Beszel is now exposed!
content/en/3.serveex/4.monitoring/5.upsnap.md
+2 -2
View File
@@ -77,7 +77,7 @@ DNS=192.168.1.1 # DNS IP to resolve domain names, typically your router’s IP
Deploy the container and go to `http://yourserverip:8095`. Just follow the steps to create your account!
### Done !
### Done!
::
::caution
@@ -195,7 +195,7 @@ server {
Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
### Done !
### Done!
::
And that’s it! You’ve exposed UpSnap!