Bot Updating Documentation

images/docker-qbittorrent.md

@@ -1,6 +1,9 @@
 ---
 title: qbittorrent
 ---
+<!-- DO NOT EDIT THIS FILE MANUALLY  -->
+<!-- Please read the https://github.com/linuxserver/docker-qbittorrent/blob/master/.github/CONTRIBUTING.md -->
+
 # [linuxserver/qbittorrent](https://github.com/linuxserver/docker-qbittorrent)
 
 [![GitHub Stars](https://img.shields.io/github/stars/linuxserver/docker-qbittorrent.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/linuxserver/docker-qbittorrent)
@@ -38,6 +41,31 @@ This image provides various versions that are available via tags. `latest` tag u
 | latest | Stable qbittorrent releases |
 | unstable | Unstable qbittorrent releases |
 
+## Application Setup
+
+The webui is at `<your-ip>:8080` and the default username/password is `admin/adminadmin`.  
+
+Change username/password via the webui in the webui section of settings.  
+
+
+### WEBUI_PORT variable
+
+Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.  
+
+For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090  
+
+This should alleviate the "white screen" issue.  
+
+If you have no webui , check the file /config/qBittorrent/qBittorrent.conf  
+
+edit or add the following lines  
+
+```
+WebUI\Address=*
+
+WebUI\ServerDomains=*
+```
+
 ## Usage
 
 Here are some example snippets to help you get started creating a container from this image.
@@ -70,7 +98,7 @@ services:
 
 ### docker cli
 
-```
+```bash
 docker run -d \
   --name=qbittorrent \
   -e PUID=1000 \
@@ -86,7 +114,6 @@ docker run -d \
   ghcr.io/linuxserver/qbittorrent
 ```
 
-
 ## Parameters
 
 Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
@@ -99,7 +126,6 @@ Docker images are configured using parameters passed at runtime (such as those a
 | `6881/udp` | udp connection port |
 | `8080` | http gui |
 
-
 ### Environment Variables (`-e`)
 
 | Env | Function |
@@ -116,15 +142,13 @@ Docker images are configured using parameters passed at runtime (such as those a
 | `/config` | Contains all relevant configuration files. |
 | `/downloads` | Location of downloads on disk. |
 
-
-
 ## Environment variables from files (Docker secrets)
 
 You can set any environment variable from a file by using a special prepend `FILE__`.
 
 As an example:
 
-```
+```bash
 -e FILE__PASSWORD=/run/secrets/mysecretpassword
 ```
 
@@ -135,7 +159,6 @@ Will set the environment variable `PASSWORD` based on the contents of the `/run/
 For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
 Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
 
-
 ## User / Group Identifiers
 
 When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
@@ -144,43 +167,17 @@ Ensure any volume directories on the host are owned by the same user you specify
 
 In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
 
-```
+```bash
   $ id username
     uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
 ```
 
-## Application Setup
-
-The webui is at `<your-ip>:8080` and the default username/password is `admin/adminadmin`.  
-
-Change username/password via the webui in the webui section of settings.  
-
-
-### WEBUI_PORT variable
-
-Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.  
-
-For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090  
-
-This should alleviate the "white screen" issue.  
-
-If you have no webui , check the file /config/qBittorrent/qBittorrent.conf  
-
-edit or add the following lines  
-
-```
-WebUI\Address=*
-
-WebUI\ServerDomains=*
-```
-
-
 ## Docker Mods
+
 [![Docker Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=qbittorrent&query=%24.mods%5B%27qbittorrent%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=qbittorrent "view available mods for this container.") [![Docker Universal Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
 
 We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
 
-
 ## Support Info
 
 * Shell access whilst the container is running: