qbittorrent

> adding stuff

qbittorrent/README.md

@@ -15,6 +15,9 @@ A script that will auto assign a category of an incoming torrent.
   <summary><strong>assign_category.py</strong> notes</summary>
 
 </details>  
+    <br />
+    <br />
+    <br />
 
 # :clipboard: Notes: `docker-compose-qbittorrent.yml`
 This docker-compose file is traditionally used to create and start a container from the command line. For Portainer we can just copy and paste this script into the web editor field.
@@ -23,49 +26,47 @@ This docker-compose file is traditionally used to create and start a container f
  </br>
 This will create two services or containers called **qbittorrent** and **qbittorrent-openvpn**.
 
-### `qbittorrent` container
+## `qbittorrent container`
 
 Key parts to this container are:
-- **image:**
+- ### **image:**
   - <a href="https://docs.linuxserver.io/images/docker-qbittorrent" target="blank">linuxserver/qbittorrent:latest</a>: &nbsp; P2P bittorrent client specially built by the linuxserver.io team.
 
-- **volumes:**
+- ### **volumes:**
   - `/home/<USERNAME>/docker/qbittorrent/custom_scripts:/custom-cont-init.d:ro`
   </br></br>
   This will be the location where the **linuxserver.io** image looks for custom scripts to run at the start of the container. Our custom script `extra_packages.sh` will need to go in this folder.</br></br>
   For more info you can see the <a href="https://docs.linuxserver.io/general/container-customization/#custom-scripts" target="blank">documentation</a>.
 
-- **ports:**
+- ###  **ports:**
   - The port section will not be used if we are using **qbittorrent-openvpn** container. All web traffic will be diverted threw that container.
 
-- **healthcheck:**
+- ###  **healthcheck:**
   - A feature of Docker that will check to see if the container is healthy or exited (bad). You will need to change `<SERVER IP ADDRESS>` to home server IP address.
   </br></br>
   In this configuration it will check to see if the container has a healthy network connection every 60 seconds. On 3 failed attempts it the container will get labeled as `exited`.</br></br>
   It is multiple ways or reasons to use **healthcheck** but for our purposes it will be used by the `inspector_qb.py` script which will reboot the container when needed.
 
-- **labels:**
+- ###  **labels:**
   - `com.centurylinklabs.watchtower.depends-on: "qbittorrent-openvpn"` - Used by watchtower to for starting and stopping containers. This container will not be rebooted before `qbittorrent-openvpn` has already done so.
 
-- **network_mode:**
+- ###  **network_mode:**
   - Tells Docker that the all network activity to container `qbittorrent` will go threw `qbittorrent-openvpn` container.
 
-- **depends_on:**
+- ###  **depends_on:**
   - Tells Docker that the container `qbittorrent` can only be run/started if `qbittorrent-openvpn` has a healthy healthcheck status.
 
----
-
-### `qbittorrent-openvpn` container
+## `qbittorrent-openvpn container`
 
 The only function of this container is to establish a **VPN** network connection.</br></br>
 Key parts to this container are:
-- **image:**
+- ###  **image:**
   - <a href="https://haugene.github.io/docker-transmission-openvpn" target="blank">haugene/transmission-openvpn</a>: &nbsp; A Docker container used as an OpenVPN network tunnel.
 
-- **cap_add:**
+- ###  **cap_add:**
   - Since we are connecting to a VPN, this container will need admin access to network related functions.
 
-- **ports:**
+- ###  **ports:**
   - This will open up ports that `qbittorrent` container will need for networking.
   </br></br>
   The web port for all `linuxserver.io` images are different in that both the `<external>:<internal>` ports have to be the same. Usually for most Docker containers your `<external>` port can change to whatever you want it to be BUT the `<internal>` port will have to stay the same.</br></br>
@@ -77,7 +78,7 @@ Key parts to this container are:
     6881:6881/udp # qbittorrent udp connection port
     ```
     
-- **environment**
+- ###  **environment**
   - **OpenVPN Provider Info:** This is where you will enter your credentials from your VPN provider.</BR></BR>
   I am using `Privado` for my VPN connection. You can use any provider that uses OpenVPN connections. For a list of supported providers that this container can use <a href="https://haugene.github.io/docker-transmission-openvpn/supported-providers" target="blank">go here</a>. You can also find the correct name to put in the `OPENVPN_PROVIDER` section on the same part of the website.
     </BR></BR>
@@ -90,17 +91,19 @@ Key parts to this container are:
 
   - **Local Network:** When the VPN has a successful connection, you wont be able to get to `qbittorrent` web gui. By setting this to your local network IP address range you will be able to access the gui from any IP address on your side of the router. To access the gui outside of your house, you will need to set up a reverse proxy in Synology NAS or similar.
 
-
 </details>  
+    <br />
+    <br />
+    <br />
+
 
 # :clipboard: Notes: `extra_packages.sh`
 A script that will be executed when the `qbittorrent` container is starting.
 
 <details>
-  <summary><strong>extra_packages.sh</strong> notes</summary>
-</br>
-This script goes in the `/custom_script` volume folder for **qbittorrent** container. It will install three programs.
+  <summary><strong>extra_packages.sh</strong> notes</summary></br>
 
+This script goes in the `/custom_script` volume folder for **qbittorrent** container. It will install three programs.
 - **python3:** This is the dependant programming language needed.
 - **pip3:** Package install for python. 
 - **qbittorrent-api:** Client API used to interact with qbittorrent over web or CLI.
@@ -133,3 +136,7 @@ apk add py3-qbittorrent-api
 
 ></br>**Note:** &nbsp;All `echo` lines will be printed out to the logs and the terminal. This way if for whatever reason the script is not working you can search the logs to troubleshoot the issue.</br>&nbsp;
 </details>
+    <br />
+    <br />
+    <br />
+    <br />