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

Add Uptime-Kuma introduction, write descriptive alt text site-wide, and fix brand capitalization and filenames with spaces

Browse Source
This commit is contained in:
Djeex
2026-09-07 14:35:25 +02:00
parent eff68287f2
commit 67d593cb73
90 changed files with 380 additions and 376 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/3.serveex/8.development/1.code-server.md
+3 -3
View File
@@ -118,8 +118,8 @@ services:
```
Once inside VS Code, you'll have access to the mounted folder.
## Expose code-server with Swag
The whole point of such a solution is to access it remotely from any device. To do this, we’ll expose code-server via Swag.
## Expose code-server with SWAG
The whole point of such a solution is to access it remotely from any device. To do this, we’ll expose code-server via SWAG.
::note
@@ -157,7 +157,7 @@ Redeploy the stack by clicking “deploy” and wait until SWAG is fully operati
### Create the subdomain.conf file
Inside the Swag config folders, create the file `code.subdomain.conf`.
Inside the SWAG config folders, create the file `code.subdomain.conf`.
::tip{icon="" to="/serveex/files/file-browser-quantum"}
✨ __Tip:__ You can use **File Browser Quantum** to navigate and edit your files instead of using terminal commands.
content/en/3.serveex/8.development/2.forgejo.md
+3 -3
View File
@@ -73,8 +73,8 @@ Deploy the container and go to `http://yourserverip:3333`. Your Forgejo instance
__If it fails:__ check your firewall rules.
::
## Exposing Forgejo with Swag
The benefit of this setup is being able to access it remotely from any of your devices. To do so, we’ll expose Forgejo through Swag.
## Exposing Forgejo with SWAG
The benefit of this setup is being able to access it remotely from any of your devices. To do so, we’ll expose Forgejo through SWAG.
::note
@@ -112,7 +112,7 @@ Redeploy the stack by clicking "Deploy" and wait until SWAG is fully operational
### Create the subdomain.conf file
Inside the Swag folders, create the file `forgejo.subdomain.conf`.
Inside the SWAG folders, create the file `forgejo.subdomain.conf`.
::tip{icon="" to="/serveex/files/file-browser-quantum"}
✨ __Tip:__ You can use **File Browser Quantum** to navigate and edit your files instead of using terminal commands.
content/en/3.serveex/8.development/3.it-tools.md
+3 -3
View File
@@ -51,8 +51,8 @@ Deploy the container and visit `http://yourserverip:3222`. That’s it, your IT
__If it fails:__ check your firewall rules.
::
## Expose IT Tools with Swag
You might want to access it remotely on all your devices. To do that, we'll expose IT Tools using Swag.
## Expose IT Tools with SWAG
You might want to access it remotely on all your devices. To do that, we'll expose IT Tools using SWAG.
::note
@@ -95,7 +95,7 @@ Restart the stack by clicking "deploy" and wait for SWAG to be fully operational
### Create the subdomain.conf file
Inside the Swag folders, create the file `tools.subdomain.conf`.
Inside the SWAG folders, create the file `tools.subdomain.conf`.
::tip{icon="" to="/serveex/files/file-browser-quantum"}
✨ __Tip:__ You can use **File Browser Quantum** to navigate and edit your files instead of using terminal commands.