Updated docs

bash/fancy_motd.sh

@@ -1,13 +1,16 @@
 #!/bin/bash
+# * Sample Output: https://i.imgur.com/dkQzkp5.jpg
 
 # Attempt to clear screen (may not work with MOTDs)
 /usr/bin/clear
 
 # Add padding
 echo -e ""
 
+# You need an image for this to work
 # Generate the image representation using chafa
-IMAGE_OUTPUT=$(chafa --size=50 /home/kk/KK.png)
+# * sudo apt install -y chafa
+IMAGE_OUTPUT=$(chafa --size=50 /home/user/logo.png)
 
 # Split the image output into an array of lines
 IFS=$'\n' read -rd '' -a IMAGE_LINES <<< "$IMAGE_OUTPUT"

docker-compose/homeassistant/configuration.yaml

@@ -13,6 +13,7 @@ script: !include scripts.yaml
 scene: !include scenes.yaml
 
 sensor:
+  # The below sensor is if you are using the qbittorrent+gluetun stack.
   - platform: command_line
     name: qBittorrent Public IP
     command: 'docker exec qbittorrent curl -s ifconfig.me'

docker-compose/qbitorrent+tor/docker-compose.yml

@@ -1,8 +1,16 @@
-# Torrent from qBittorrent through the Tor network
+# Torrent from qBittorrent through the Tor network (not recommended)
+# If you can, use qbittorrent+gluetun instead.
 # Beware: It will be often dead slow
 
-# Purely for educational purposes and not intended for illegal use
-# 
+# Purely for educational purposes and not intended for illegal use.
+
+# ! Why should we not use Tor for torrenting?
+# * Torrenting via Tor strains limited bandwidth, degrading performance for others. 
+# *   Torrent clients can leak your real IP, compromising anonymity. 
+# *   Tor exit nodes face legal risks from torrent traffic. 
+# *   Tor isn't optimized for high-bandwidth tasks like torrenting. 
+# *   Some exit nodes block BitTorrent due to these issues.
+# *   Not to mention, they don't support UDP, which is required for DHT and PEX. 
 
 version: '3'
 services: