diff --git a/content/2.general/1.networking/2.dns.md b/content/2.general/1.networking/2.dns.md
index d3b31b3..a6c61d7 100644
--- a/content/2.general/1.networking/2.dns.md
+++ b/content/2.general/1.networking/2.dns.md
@@ -55,7 +55,7 @@ So, if you want to point `mydomain.com` to your server, you can do it by adding
- __Warning:__ If your server is hosted at home:
:::
- Your public IP is the one assigned to your home router. Make sure it's static, or configure [DDNS](https://aws.amazon.com/fr/what-is/dynamic-dns/).
-- Make sure you've [set up port 443 forwarding to your server's listening port](/general/nat).
+- Make sure you've [set up port 443 forwarding to your server's listening port](/general/networking/nat).
::
If you're adding a subdomain that should also point to your server, use a `CNAME` record pointing to `mydomain.com`.
diff --git a/content/2.general/2.storage/2.zfs.md b/content/2.general/2.storage/2.zfs.md
index 5f7cfe4..2040739 100644
--- a/content/2.general/2.storage/2.zfs.md
+++ b/content/2.general/2.storage/2.zfs.md
@@ -21,7 +21,7 @@ To put it simply:
ZFS goes far beyond traditional file systems in terms of performance and features.
Here’s what we’re most interested in:
- Its __snapshot management__ features, allowing you to quickly roll back in case of issues.
-- Its support for disk groupings and [__RAID-like structures__](/general/raid) (Z-Mirror, RAIDZ1, RAIDZ2, RAIDZ3).
+- Its support for disk groupings and [__RAID-like structures__](/general/storage/raid) (Z-Mirror, RAIDZ1, RAIDZ2, RAIDZ3).
- Its __automatic recovery of corrupted data__ (through scrubbing).
- Its performance, enhanced by RAM caching (ZFS ARC).
- Its robust error notifications and monitoring.
@@ -49,7 +49,7 @@ ZFS continuously checks that your stored data hasn't become corrupted. Every blo
### Built-in RAID
-ZFS includes its own volume management system (vdevs). You can build a zpool using multiple disks—similar to traditional [RAID](/general/raid) setups—but with more flexibility. For example:
+ZFS includes its own volume management system (vdevs). You can build a zpool using multiple disks—similar to traditional [RAID](/general/storage/raid) setups—but with more flexibility. For example:
- **Z-mirror** → equivalent to RAID 1
- **RAIDZ1** → equivalent to RAID 5 (tolerates 1 disk failure)
- **RAIDZ2** → equivalent to RAID 6 (tolerates 2 disk failures)
@@ -59,7 +59,7 @@ ZFS handles all this natively—no external RAID software needed.
::alert{type="info"}
:::list{type="info"}
-- Check out the [article on RAID](/general/raid) to find the right solution for your needs.
+- Check out the [article on RAID](/general/storage/raid) to find the right solution for your needs.
:::
::
diff --git a/content/2.general/_dir.yml b/content/2.general/_dir.yml
index 14a38ba..4ce8f06 100644
--- a/content/2.general/_dir.yml
+++ b/content/2.general/_dir.yml
@@ -1,3 +1,3 @@
icon: noto:open-book
navigation.title: General
-navigation.redirect: /general/nat
+navigation.redirect: /general/networking/nat
diff --git a/content/3.serveex/1.introduction.md b/content/3.serveex/1.introduction.md
index a2abb6c..a185d3e 100644
--- a/content/3.serveex/1.introduction.md
+++ b/content/3.serveex/1.introduction.md
@@ -18,8 +18,8 @@ A big thanks to **Nipah** for sharing his infinite knowledge and, above all, for
**Prerequisites:**
:::list{type="primary"}
- Have [an online VPS](https://www.it-connect.fr/les-serveurs-prives-virtuels-vps-pour-les-debutants/) or a local machine: ideally a mini PC (you can find N100 models for around €100), but it also works on a laptop or [a virtual machine](https://openclassrooms.com/fr/courses/2035806-virtualisez-votre-architecture-et-vos-environnements-de-travail/6313946-installez-virtualbox). The [Freebox Delta/Ultra offer virtual machines](https://next.ink/3493/machines-virtuelles-et-freebox-delta-comment-heberger-votre-premiere-page-web/).
-- Know how to configure [NAT rules on a router and assign DHCP leases](/general/nat)
-- Know how to configure the [DNS zone of a domain name](/general/dns)
+- Know how to configure [NAT rules on a router and assign DHCP leases](/general/networking/nat)
+- Know how to configure the [DNS zone of a domain name](/general/networking/dns)
:::
::
diff --git a/content/3.serveex/2.core/1.installation.md b/content/3.serveex/2.core/1.installation.md
index 3d8805d..0a0266e 100644
--- a/content/3.serveex/2.core/1.installation.md
+++ b/content/3.serveex/2.core/1.installation.md
@@ -60,7 +60,7 @@ Additionally:
- [Firewalld](https://linuxcapable.com/how-to-install-firewalld-on-debian-linux/)
### Samba Sharing (Access a Remote Network Disk)
-- [Create and Access a Samba Share](/general/samba)
+- [Create and Access a Samba Share](/general/networking/samba)
### File Transfer via rsync
diff --git a/content/3.serveex/2.core/3.swag.md b/content/3.serveex/2.core/3.swag.md
index f8ac2f4..51134ac 100644
--- a/content/3.serveex/2.core/3.swag.md
+++ b/content/3.serveex/2.core/3.swag.md
@@ -265,7 +265,7 @@ server {
---
::alert{type="info"}
📋 __Prerequisite:__
-We assume that you have created a subdomain like `dockge.mydomain.com` in your [DNS zone](/general/dns), with a `CNAME` pointing to `mydomain.com` and — unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare) — that you've forwarded port `443` from your router to the server's `443` in [your NAT rules](/general/nat).
+We assume that you have created a subdomain like `dockge.mydomain.com` in your [DNS zone](/general/networking/dns), with a `CNAME` pointing to `mydomain.com` and — unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare) — that you've forwarded port `443` from your router to the server's `443` in [your NAT rules](/general/networking/nat).
::
Now it's time to expose Dockge on the internet so you can access and manage your containers remotely. We assume you've set up the subdomain `dockge.mydomain.com` with a `CNAME` pointing to `mydomain.com`.
diff --git a/content/3.serveex/3.security/2.authentik.md b/content/3.serveex/3.security/2.authentik.md
index 74ae88a..d5c2b46 100644
--- a/content/3.serveex/3.security/2.authentik.md
+++ b/content/3.serveex/3.security/2.authentik.md
@@ -195,7 +195,7 @@ To use Authentik outside your local network, you must expose it.
::alert{type="info"}
📋 __Prerequisites:__
-We assume you have already created a subdomain like `auth.mydomain.com` in your [DNS zone](/general/dns), with a CNAME pointing to `mydomain.com`. Also, unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare), you must have already forwarded port `443` from your router to port `443` of your server in your [NAT rules](/general/nat).
+We assume you have already created a subdomain like `auth.mydomain.com` in your [DNS zone](/general/networking/dns), with a CNAME pointing to `mydomain.com`. Also, unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare), you must have already forwarded port `443` from your router to port `443` of your server in your [NAT rules](/general/networking/nat).
::
Open the `authentik-server.conf` file:
diff --git a/content/3.serveex/3.security/3.cloudflare.md b/content/3.serveex/3.security/3.cloudflare.md
index 837af58..d19e93b 100644
--- a/content/3.serveex/3.security/3.cloudflare.md
+++ b/content/3.serveex/3.security/3.cloudflare.md
@@ -46,7 +46,7 @@ Here we’ll explain how to integrate SWAG with Cloudflare tunnels.
---
### DNS Zone
-First, you need to set Cloudflare as your [DNS zone](/general/dns) manager. If you bought your domain from Cloudflare, that’s already done. Otherwise, check with your registrar how to add external DNS servers. Cloudflare provides [step-by-step documentation](https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/) on how to configure a DNS Zone, whether your domain is external or registered with Cloudflare.
+First, you need to set Cloudflare as your [DNS zone](/general/networking/dns) manager. If you bought your domain from Cloudflare, that’s already done. Otherwise, check with your registrar how to add external DNS servers. Cloudflare provides [step-by-step documentation](https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/) on how to configure a DNS Zone, whether your domain is external or registered with Cloudflare.
If you only have one server to protect behind Cloudflare, you can delete all existing DNS records. By default, your domain and all its subdomains will be redirected to the tunnel.
@@ -214,10 +214,10 @@ TUNNEL_PW=
Once done, deploy the stack. Check the logs—you should reach `server ready`.
-Then confirm your tunnel appears under _Networks > Tunnels_ in [Cloudflare Zero Trust](https://one.dash.cloudflare.com/). By default, all subdomains will be routed through the tunnel—no need to define them [in your DNS zone](/general/dns).
+Then confirm your tunnel appears under _Networks > Tunnels_ in [Cloudflare Zero Trust](https://one.dash.cloudflare.com/). By default, all subdomains will be routed through the tunnel—no need to define them [in your DNS zone](/general/networking/dns).
::alert{type="success"}
-✨ __Tip:__ If you want to expose a service without a tunnel, just define an A record [in your DNS zone](/general/dns). If resolution fails, disable the proxy function for that record—e.g., for `sub.mondomaine.fr`.
+✨ __Tip:__ If you want to expose a service without a tunnel, just define an A record [in your DNS zone](/general/networking/dns). If resolution fails, disable the proxy function for that record—e.g., for `sub.mondomaine.fr`.
::
diff --git a/content/3.serveex/4.monitoring/1.uptime-kuma.md b/content/3.serveex/4.monitoring/1.uptime-kuma.md
index 34721bc..d208048 100644
--- a/content/3.serveex/4.monitoring/1.uptime-kuma.md
+++ b/content/3.serveex/4.monitoring/1.uptime-kuma.md
@@ -68,7 +68,7 @@ You can now access the tool via `http://yourserverip:3200`.
::alert{type="info"}
📋 __Before you begin:__
-We assume you have the subdomain `stats.mydomain.com` with a `CNAME` pointing to `mydomain.com` in your [DNS zone](/general/dns). And of course, [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` of your router should point to port `443` of your server via [NAT rules](/general/nat).
+We assume you have the subdomain `stats.mydomain.com` with a `CNAME` pointing to `mydomain.com` in your [DNS zone](/general/networking/dns). And of course, [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` of your router should point to port `443` of your server via [NAT rules](/general/networking/nat).
::
::alert{type="warning"}
diff --git a/content/3.serveex/4.monitoring/2.dozzle.md b/content/3.serveex/4.monitoring/2.dozzle.md
index f0ea065..d314b5d 100644
--- a/content/3.serveex/4.monitoring/2.dozzle.md
+++ b/content/3.serveex/4.monitoring/2.dozzle.md
@@ -79,7 +79,7 @@ You may want to access Dozzle remotely and on all your devices. To do so, we’l
::alert{type="info"}
📋 __Before you begin:__
-We assume you have created a subdomain like `dozzle.mydomain.com` in your [DNS zone](/general/dns) with a `CNAME` pointing to `mydomain.com` and that, [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), you’ve redirected port `443` from your router to port `443` on your server in your [NAT rules](/general/nat).
+We assume you have created a subdomain like `dozzle.mydomain.com` in your [DNS zone](/general/networking/dns) with a `CNAME` pointing to `mydomain.com` and that, [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), you’ve redirected port `443` from your router to port `443` on your server in your [NAT rules](/general/networking/nat).
::
Go to Dockge and edit the SWAG compose file to add Dozzle’s network:
diff --git a/content/3.serveex/4.monitoring/3.speedtest-tracker.md b/content/3.serveex/4.monitoring/3.speedtest-tracker.md
index 4e744e4..db7e903 100644
--- a/content/3.serveex/4.monitoring/3.speedtest-tracker.md
+++ b/content/3.serveex/4.monitoring/3.speedtest-tracker.md
@@ -91,7 +91,7 @@ Deploy the container and go to `http://yourserverip:3225`. Log in with the accou
---
::alert{type="info"}
📋 **Prerequisites:**
-We assume that you've already created a subdomain like `speedtest.yourdomain.com` in your [DNS zone](/general/dns) with a `CNAME` pointing to `yourdomain.com`, and [unless you’re using Cloudflare Zero Trust](/serveex/security/cloudflare), you've also forwarded port `443` from your router to port `443` of your server in your [NAT rules](/general/nat).
+We assume that you've already created a subdomain like `speedtest.yourdomain.com` in your [DNS zone](/general/networking/dns) with a `CNAME` pointing to `yourdomain.com`, and [unless you’re using Cloudflare Zero Trust](/serveex/security/cloudflare), you've also forwarded port `443` from your router to port `443` of your server in your [NAT rules](/general/networking/nat).
::
Now we want to expose Speedtest Tracker to the internet so you can access it remotely. We assume you've set up the DNS `CNAME` for `speedtest.yourdomain.com` pointing to `yourdomain.com`.
diff --git a/content/3.serveex/4.monitoring/4.beszel.md b/content/3.serveex/4.monitoring/4.beszel.md
index 6cbea15..0b7e8a9 100644
--- a/content/3.serveex/4.monitoring/4.beszel.md
+++ b/content/3.serveex/4.monitoring/4.beszel.md
@@ -156,7 +156,7 @@ If you want to access Beszel remotely from all your devices, expose it using Swa
::alert{type="info"}
📋 __Prerequisite:__
-You must have created a DNS subdomain like `beszel.mydomain.com` with a `CNAME` pointing to `mydomain.com`, and—unless you're using Cloudflare Zero Trust—you must have forwarded port `443` on your router to your server’s `443` port via [NAT rules](/general/nat).
+You must have created a DNS subdomain like `beszel.mydomain.com` with a `CNAME` pointing to `mydomain.com`, and—unless you're using Cloudflare Zero Trust—you must have forwarded port `443` on your router to your server’s `443` port via [NAT rules](/general/networking/nat).
::
In Dockge, edit Swag's compose file and add Beszel’s network:
diff --git a/content/3.serveex/4.monitoring/5.upsnap.md b/content/3.serveex/4.monitoring/5.upsnap.md
index 5f06b04..a23900c 100644
--- a/content/3.serveex/4.monitoring/5.upsnap.md
+++ b/content/3.serveex/4.monitoring/5.upsnap.md
@@ -94,7 +94,7 @@ You may want to access it remotely from all your devices. To do so, we'll expose
::alert{type="info"}
📋 __Beforehand:__
-We assume you've created a subdomain in your [DNS zone](/general/dns), such as `upsnap.yourdomain.com` with a `CNAME` to `yourdomain.com`. Also, unless you're using Cloudflare Zero Trust, you should have already forwarded port `443` from your router to port `443` on your server in your [NAT rules](/general/nat).
+We assume you've created a subdomain in your [DNS zone](/general/networking/dns), such as `upsnap.yourdomain.com` with a `CNAME` to `yourdomain.com`. Also, unless you're using Cloudflare Zero Trust, you should have already forwarded port `443` from your router to port `443` on your server in your [NAT rules](/general/networking/nat).
::
Go to Dockge, and edit the SWAG compose by adding the UpSnap network:
diff --git a/content/3.serveex/5.media/1.plex.md b/content/3.serveex/5.media/1.plex.md
index 770e153..0264afd 100644
--- a/content/3.serveex/5.media/1.plex.md
+++ b/content/3.serveex/5.media/1.plex.md
@@ -144,7 +144,7 @@ Then go to the _Remote Access_ section and manually select a port (we’ll use `
-- On your router, forward TCP port `1234` to port `32400` for your server’s IP using [NAT rules](/general/nat).
+- On your router, forward TCP port `1234` to port `32400` for your server’s IP using [NAT rules](/general/networking/nat).
- Once done, return to Plex to verify that remote access is functional.
::alert{type="danger"}
@@ -163,7 +163,7 @@ Simply add your media to `/media/movies` and `/media/tvseries` on your server. Y
::alert{type="info"}
:::list{type="info"}
-- If your media is stored on a network disk (e.g. NAS or external hard drive over the network), refer to the [Samba mount guide](/general/samba) so Plex can access it.
+- If your media is stored on a network disk (e.g. NAS or external hard drive over the network), refer to the [Samba mount guide](/general/networking/samba) so Plex can access it.
:::
::
@@ -175,7 +175,7 @@ However, you may want to expose Tautulli so you can view stats from a simple URL
::alert{type="info"}
:::list{type="info"}
-- We assume you have the subdomain `tautulli.mydomain.com` with a `CNAME` pointing to `mydomain.com` in your [DNS zone](/general/dns). And of course, [unless you use Cloudflare Zero Trust](/serveex/security/cloudflare), your box's port `443` must be forwarded to your server's port `443` in [NAT rules](/general/nat).
+- We assume you have the subdomain `tautulli.mydomain.com` with a `CNAME` pointing to `mydomain.com` in your [DNS zone](/general/networking/dns). And of course, [unless you use Cloudflare Zero Trust](/serveex/security/cloudflare), your box's port `443` must be forwarded to your server's port `443` in [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/5.media/2.qbittorrent.md b/content/3.serveex/5.media/2.qbittorrent.md
index 38ce62a..2f62ccd 100644
--- a/content/3.serveex/5.media/2.qbittorrent.md
+++ b/content/3.serveex/5.media/2.qbittorrent.md
@@ -217,7 +217,7 @@ To start downloads from outside your home, without a VPN, you can expose the Qbi
::alert{type="info"}
:::list{type="info"}
-- We assume you have the subdomain `seedbox.mydomain.com` with a `CNAME` pointing to `mydomain.com` in [DNS zone](/general/dns). And that port `443` on your router is forwarded to your server in [NAT rules](/general/nat), unless you’re using Cloudflare Zero Trust.
+- We assume you have the subdomain `seedbox.mydomain.com` with a `CNAME` pointing to `mydomain.com` in [DNS zone](/general/networking/dns). And that port `443` on your router is forwarded to your server in [NAT rules](/general/networking/nat), unless you’re using Cloudflare Zero Trust.
:::
::
diff --git a/content/3.serveex/5.media/3.servarr.md b/content/3.serveex/5.media/3.servarr.md
index dc0c551..8677930 100644
--- a/content/3.serveex/5.media/3.servarr.md
+++ b/content/3.serveex/5.media/3.servarr.md
@@ -394,7 +394,7 @@ It can be useful to expose Overseerr if you want to send requests from outside y
::alert{type="info"}
:::list{type="info"}
-- We assume you have the subdomain `films.mydomain.com` with a `CNAME` pointing to `films.fr` in your [DNS zone](/general/dns). And that [unless you’re using Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` on your router is forwarded to port `443` on your server via [NAT rules](/general/nat).
+- We assume you have the subdomain `films.mydomain.com` with a `CNAME` pointing to `films.fr` in your [DNS zone](/general/networking/dns). And that [unless you’re using Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` on your router is forwarded to port `443` on your server via [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/6.cloud/1.immich.md b/content/3.serveex/6.cloud/1.immich.md
index 24066af..a9c8a76 100644
--- a/content/3.serveex/6.cloud/1.immich.md
+++ b/content/3.serveex/6.cloud/1.immich.md
@@ -40,7 +40,7 @@ Configure the `.env` file by copying the latest version [from here](https://gith
::alert{type="info"}
:::list{type="info"}
-- If you're using a NAS or a network-shared drive via [Samba](/general/samba/) to store your data, replace the value of `UPLOAD_LOCATION`{lang=properties} with the path to your shared folder.
+- If you're using a NAS or a network-shared drive via [Samba](/general/networking/samba/) to store your data, replace the value of `UPLOAD_LOCATION`{lang=properties} with the path to your shared folder.
:::
::
@@ -59,7 +59,7 @@ The main benefit of this setup is being able to access Immich remotely on all yo
::alert{type="info"}
📋 __Before you begin:__
-We assume that you have a subdomain `immich.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/dns). Also, unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare), make sure port `443` on your router is forwarded to port `443` on your server via [NAT rules](/general/nat).
+We assume that you have a subdomain `immich.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/networking/dns). Also, unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare), make sure port `443` on your router is forwarded to port `443` on your server via [NAT rules](/general/networking/nat).
::
In Dockge, open the SWAG stack and edit the compose file to add Immich's network:
diff --git a/content/3.serveex/6.cloud/2.nextcloud.md b/content/3.serveex/6.cloud/2.nextcloud.md
index 8629bd3..692056f 100644
--- a/content/3.serveex/6.cloud/2.nextcloud.md
+++ b/content/3.serveex/6.cloud/2.nextcloud.md
@@ -57,7 +57,7 @@ services:
::alert{type="info"}
:::list{type="info"}
-- If you’re using a NAS or network-shared drive via [Samba](/general/samba), replace `/docker/nextcloud/data` with the path to your shared folder.
+- If you’re using a NAS or network-shared drive via [Samba](/general/networking/samba), replace `/docker/nextcloud/data` with the path to your shared folder.
:::
::
@@ -89,7 +89,7 @@ The goal of this setup is to access Nextcloud remotely from all your devices. We
::alert{type="info"}
:::list{type="info"}
-- We assume you have a subdomain `nextcloud.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/dns). And unless you’re using [Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` on your router must be forwarded to port `443` on your server using [NAT rules](/general/nat).
+- We assume you have a subdomain `nextcloud.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/networking/dns). And unless you’re using [Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` on your router must be forwarded to port `443` on your server using [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/7.files/1.file-browser.md b/content/3.serveex/7.files/1.file-browser.md
index 60fce7a..00292d5 100644
--- a/content/3.serveex/7.files/1.file-browser.md
+++ b/content/3.serveex/7.files/1.file-browser.md
@@ -66,7 +66,7 @@ You may want to access File Browser remotely from all your devices. To do that,
::alert{type="info"}
:::list{type="info"}
-- __Pre-requisite:__ We assume you've already created a subdomain like `files.yourdomain.com` in your [DNS zone](/general/dns) pointing to `yourdomain.com` with a `CNAME`, and—unless you're using Cloudflare Zero Trust—have already forwarded port `443` on your router to port `443` on your server using [NAT rules](/general/nat).
+- __Pre-requisite:__ We assume you've already created a subdomain like `files.yourdomain.com` in your [DNS zone](/general/networking/dns) pointing to `yourdomain.com` with a `CNAME`, and—unless you're using Cloudflare Zero Trust—have already forwarded port `443` on your router to port `443` on your server using [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/7.files/2.pingvin.md b/content/3.serveex/7.files/2.pingvin.md
index 25ffb2a..a80633d 100644
--- a/content/3.serveex/7.files/2.pingvin.md
+++ b/content/3.serveex/7.files/2.pingvin.md
@@ -81,7 +81,7 @@ Tout l'intérêt d'une telle solution, c'est de pouvoir y accéder à distance e
::alert{type="info"}
📋 __Au préalable :__
-Nous partons du principe que vous avez le sous-domaine `pingvin.mondomaine.fr` avec un `CNAME` qui pointe vers `mondomaine.fr` dans votre [zone DNS](/general/dns). Et que bien sûr, [à moins que vous utilisiez Cloudflare Zero Trust](/serveex/security/cloudflare), le port `443` de votre box pointe bien sur le port `443` de votre serveur via [les règles NAT](/general/nat).
+Nous partons du principe que vous avez le sous-domaine `pingvin.mondomaine.fr` avec un `CNAME` qui pointe vers `mondomaine.fr` dans votre [zone DNS](/general/networking/dns). Et que bien sûr, [à moins que vous utilisiez Cloudflare Zero Trust](/serveex/security/cloudflare), le port `443` de votre box pointe bien sur le port `443` de votre serveur via [les règles NAT](/general/networking/nat).
::
Dans Dockge, rendez-vous dans la stack de SWAG et éditez le compose en ajoutant le réseau de pingvin :
diff --git a/content/3.serveex/8.development/1.code-server.md b/content/3.serveex/8.development/1.code-server.md
index c8040a1..d533470 100644
--- a/content/3.serveex/8.development/1.code-server.md
+++ b/content/3.serveex/8.development/1.code-server.md
@@ -122,7 +122,7 @@ The whole point of such a solution is to access it remotely from any device. To
::alert{type="info"}
:::list{type="info"}
-- __Preliminary:__ We assume you’ve created a subdomain like `code.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/dns), and—unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare)—that you’ve forwarded port `443` from your router to port `443` on your server using [NAT rules](/general/nat).
+- __Preliminary:__ We assume you’ve created a subdomain like `code.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/networking/dns), and—unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare)—that you’ve forwarded port `443` from your router to port `443` on your server using [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/8.development/2.gitea.md b/content/3.serveex/8.development/2.gitea.md
index 50f7721..d110df9 100644
--- a/content/3.serveex/8.development/2.gitea.md
+++ b/content/3.serveex/8.development/2.gitea.md
@@ -74,7 +74,7 @@ The benefit of this setup is being able to access it remotely from any of your d
::alert{type="info"}
:::list{type="info"}
-- __Prerequisite:__ We assume you have created a subdomain such as `gitea.yourdomain.com` in your [DNS zone](/general/dns) with `CNAME` pointing to `yourdomain.com`, and [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), you have already forwarded port `443` from your router to your server’s port `443` in the [NAT rules](/general/nat).
+- __Prerequisite:__ We assume you have created a subdomain such as `gitea.yourdomain.com` in your [DNS zone](/general/networking/dns) with `CNAME` pointing to `yourdomain.com`, and [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), you have already forwarded port `443` from your router to your server’s port `443` in the [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/8.development/3.it-tools.md b/content/3.serveex/8.development/3.it-tools.md
index ba1d600..98efd78 100644
--- a/content/3.serveex/8.development/3.it-tools.md
+++ b/content/3.serveex/8.development/3.it-tools.md
@@ -58,7 +58,7 @@ You might want to access it remotely on all your devices. To do that, we'll expo
::alert{type="info"}
:::list{type="info"}
-- __Pre-requisite:__ We assume you’ve created a subdomain like `tools.yourdomain.com` in your [DNS zone](/general/dns) with `CNAME` set to `yourdomain.com`. Also, unless you’re using [Cloudflare Zero Trust](/serveex/security/cloudflare), make sure you’ve already forwarded port `443` from your router to port `443` on your server in the [NAT rules](/general/nat).
+- __Pre-requisite:__ We assume you’ve created a subdomain like `tools.yourdomain.com` in your [DNS zone](/general/networking/dns) with `CNAME` set to `yourdomain.com`. Also, unless you’re using [Cloudflare Zero Trust](/serveex/security/cloudflare), make sure you’ve already forwarded port `443` from your router to port `443` on your server in the [NAT rules](/general/networking/nat).
:::
::
diff --git a/content/3.serveex/9.apps/1.adguard.md b/content/3.serveex/9.apps/1.adguard.md
index a8f30f4..3264963 100644
--- a/content/3.serveex/9.apps/1.adguard.md
+++ b/content/3.serveex/9.apps/1.adguard.md
@@ -104,7 +104,7 @@ To make AdGuard usable from outside your home network, you need to expose it.
::alert{type="info"}
:::list{type="info"}
-- __Prerequisites:__ We assume you've created a subdomain like `adguard.mydomain.com` in your [DNS zone](/general/dns) with a `CNAME` pointing to `mydomain.com`, and that you’ve already forwarded port `443` from your router to port `443` on your server in your [NAT rules](/general/nat). Also forward port `53` and port `853` to your server. These ports are used to route DNS requests.
+- __Prerequisites:__ We assume you've created a subdomain like `adguard.mydomain.com` in your [DNS zone](/general/networking/dns) with a `CNAME` pointing to `mydomain.com`, and that you’ve already forwarded port `443` from your router to port `443` on your server in your [NAT rules](/general/networking/nat). Also forward port `53` and port `853` to your server. These ports are used to route DNS requests.
:::
::
diff --git a/content/3.serveex/9.apps/2.vaultwarden.md b/content/3.serveex/9.apps/2.vaultwarden.md
index 432c196..a17e3ec 100644
--- a/content/3.serveex/9.apps/2.vaultwarden.md
+++ b/content/3.serveex/9.apps/2.vaultwarden.md
@@ -108,7 +108,7 @@ Recently, Vaultwarden requires SSL to be accessed, which prevents access via a l
The main benefit of Vaultwarden is being able to access it remotely from any device. We'll expose it through [SWAG](/serveex/core/swag).
::alert{type="info"}
-✨ __Before you start:__ Make sure you've created a DNS subdomain like `vault.yourdomain.com` with `CNAME` pointing to `yourdomain.com` and (unless using Cloudflare Zero Trust) that you've forwarded port `443` from your router to your server's `443` via [NAT rules](/general/nat).
+✨ __Before you start:__ Make sure you've created a DNS subdomain like `vault.yourdomain.com` with `CNAME` pointing to `yourdomain.com` and (unless using Cloudflare Zero Trust) that you've forwarded port `443` from your router to your server's `443` via [NAT rules](/general/networking/nat).
::
In Dockge, go to the SWAG stack and edit the compose file to add the Vaultwarden network:
diff --git a/content/5.nonsense/2.bash/1.servarr-duplicates.md b/content/5.nonsense/2.bash/1.servarr-duplicates.md
index 8ea7d8a..d7a08c7 100644
--- a/content/5.nonsense/2.bash/1.servarr-duplicates.md
+++ b/content/5.nonsense/2.bash/1.servarr-duplicates.md
@@ -1,6 +1,6 @@
---
navigation: true
-title: Bash Scripts
+title: Servarr corrector
main:
fluid: false
---