Bot Updating Documentation

* Add split dns

* CR fixes

* Fix typo

* CR fixes

docs/general/.pages

@@ -10,3 +10,4 @@ nav:
     - fleet.md
     - swag.md
     - how-to-get-support.md
+    - split-dns.md

docs/general/split-dns.md

@@ -0,0 +1,69 @@
+![Split DNS](../assets/images/split-dns.png)
+
+# Split DNS
+
+Spilt DNS allows you to give different answers to DNS requests for internal and external users, so local requests for your server don't have to go via your router, it has several benefits:
+
+- Faster due to not having to go through the router.
+- The reverse proxy can easily differentiate between internal and external requests with allow/deny since there's no NAT.
+- Things still work when the internet is down.
+- Things still work when upstream DNS (Your ISP/Google/OpenDNS/etc) isn't available.
+
+## Requirements
+
+- An internal reverse proxy that **listens on port 80/443**.
+- An internal DNS resolver that supports rewrites or hosting full DNS zones.
+
+## Popular DNS Configurations
+
+These examples assume `domain.com` is your domain and `10.10.10.10` is your reverse proxy.
+
+### OPNSense
+
+Navigate to Services > Unbound DNS > Overrides > Host Overrides > Add:
+
+- Host: `*`
+- Domain: `domain.com`
+- Type: `A or AAAA`
+- IP: `10.10.10.10`
+
+### PFSense
+
+Navigate to Services > DNS Resolver > General Setting > Host Overrides > Add:
+
+- Host: `*`
+- Domain: `domain.com`
+- IP Address: `10.10.10.10`
+
+### Pihole & dnsmasq
+
+Create a file called `/etc/dnsmasq.d/domain.conf` with this contents:
+
+```
+address=/domain.com/10.10.10.10
+```
+
+### AdguardHome
+
+Navigate to Filters > DNS rewrites > Add DNS rewrite:
+
+- Domain name: `*.domain.com`
+- IP Address: `10.10.10.10`
+
+## Wireguard Issues
+
+When exposing a wireguard server, the wireguard subdomain should not be split or it will break the connection while roaming between wi-fi and mobile data.
+
+For example, you can exclude `wg.domain.com` on AdguardHome by creating another DNS rewrite of `wg.domain.com` to `wg.domain.com`, that will exclude it from the split.
+
+## NAT Reflection / NAT Loopback / Hairpin NAT
+
+NAT reflection is an alternative option to split DNS, which can provide some but not all of the same same benefits, it allows LAN devices to use the external IP and get port-forwarded without being NAT'd. 
+
+It's usually a setting on specific routers that can be enabled via a checkbox.
+
+Note that using Cloudflare proxy (the orange cloud) or Cloudflare tunnels will bypass it and still send traffic externally.
+
+## Neither
+
+Without split DNS or NAT reflection traffic goes out of your router to reach your external IP and then gets NAT'd back in, often getting blocked by the router since external traffic with a LAN IP source is seen as malicious.

docs/images/docker-plex-meta-manager.md

@@ -16,9 +16,9 @@ title: plex-meta-manager
 [![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-plex-meta-manager%2Fjob%2Fmain%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-plex-meta-manager/job/main/)
 [![LSIO CI](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=CI&query=CI&url=https%3A%2F%2Fci-tests.linuxserver.io%2Flinuxserver%2Fplex-meta-manager%2Flatest%2Fci-status.yml)](https://ci-tests.linuxserver.io/linuxserver/plex-meta-manager/latest/index.html)
 
-[Plex-meta-manager](https://github.com/meisnate12/Plex-Meta-Manager) is a Python 3 script that can be continuously run using YAML configuration files to update on a schedule the metadata of the movies, shows, and collections in your libraries as well as automatically build collections based on various methods all detailed in the wiki.
+[Plex-meta-manager](https://github.com/Kometa-Team/Kometa) is a Python 3 script that can be continuously run using YAML configuration files to update on a schedule the metadata of the movies, shows, and collections in your libraries as well as automatically build collections based on various methods all detailed in the wiki.
 
-[![plex-meta-manager](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-meta-manager-banner.png)](https://github.com/meisnate12/Plex-Meta-Manager)
+[![plex-meta-manager](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-meta-manager-banner.png)](https://github.com/Kometa-Team/Kometa)
 
 ## Supported Architectures
 
@@ -46,13 +46,13 @@ This image provides various versions that are available via tags. Please read th
 
 ## Application Setup
 
-There is a [walkthrough](https://metamanager.wiki/en/latest/home/guides/docker.html#setting-up-the-initial-config-file) available to help get you up and running.
+There is a [walkthrough](https://kometa.wiki/en/latest/home/guides/docker.html#setting-up-the-initial-config-file) available to help get you up and running.
 
-This image supports all of the environment variables listed [here](https://metamanager.wiki/en/latest/home/environmental.html) and all commandline arguments.
+This image supports all of the environment variables listed [here](https://kometa.wiki/en/latest/home/environmental.html) and all commandline arguments.
 
 To perform a one-time run use `docker run` (or `docker-compose run`) with the `--rm` and `-e PMM_RUN=True` arguments. This will cause the container to process your config immediately instead of waiting for the scheduled time, and delete the old container after completion.
 
-For more information see the [official wiki](https://metamanager.wiki).
+For more information see the [official wiki](https://kometa.wiki).
 
 ## Usage
 
@@ -294,6 +294,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
 
 ## Versions
 
+* **22.04.24:** - Update backend to reflect upstream repo rename.
 * **23.12.23:** - Rebase to Alpine 3.19.
 * **10.06.23:** - Rebase to Alpine 3.18, deprecate armhf.
 * **05.03.23:** - Add nightly branch.

docs/images/docker-socket-proxy.md

@@ -35,7 +35,7 @@ Find us at:
 [![Docker Stars](https://img.shields.io/docker/stars/linuxserver/socket-proxy.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=stars&logo=docker)](https://hub.docker.com/r/linuxserver/socket-proxy)
 [![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-socket-proxy%2Fjob%2Fmain%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-socket-proxy/job/main/)
 
-Socket proxy is a security-enhanced proxy for the Docker Socket.
+The Socket Proxy is a security-enhanced proxy which allows you to apply access rules to the Docker socket, limiting the attack surface for containers such as watchtower or Traefik that need to use it.
 
 ![socket-proxy](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/docker-logo.png)
 

docs/images/docker-webtop.md

@@ -395,6 +395,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
 
 ## Versions
 
+* **22.04.24:** - Rebase Ubuntu to Noble.
 * **16.04.24:** - Add docs on PRoot Apps.
 * **14.04.24:** - Rebase Fedora to 40.
 * **11.02.24:** - Add PWA icons and title variants properly.