From 73112bcf65c555adfc3ed1d0ad25adbe3c2aba3f Mon Sep 17 00:00:00 2001 From: Robert Simplicio Date: Tue, 26 Nov 2024 17:13:51 -0800 Subject: [PATCH 1/4] Update qbit-manage.md to correct instances of qbit_manage to qbit-manage Several commands and the docker container name use a hyphen/dash rather than an underscore as the separator between qbit and manage. Updated instances where this caused an issue while following the documentation. --- docs/sandbox/apps/qbit-manage.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/sandbox/apps/qbit-manage.md b/docs/sandbox/apps/qbit-manage.md index 341ef05fd..1b48b43bb 100644 --- a/docs/sandbox/apps/qbit-manage.md +++ b/docs/sandbox/apps/qbit-manage.md @@ -41,10 +41,10 @@ sb install sandbox-qbit-manage ``` -After installation has finished, stop the qbit_manage docker container and edit the config file that will have been created at `/opt/qbit_manage/config.yml` +After installation has finished, stop the qbit-manage docker container and edit the config file that will have been created at `/opt/qbit-manage/config.yml` ```shell -docker stop qbit_manage +docker stop qbit-manage ``` Minimally you will need to change the following items in order to connect with your qBittorrent instance:- @@ -68,10 +68,10 @@ The config file is full of examples that more than likely will not work for you, After making adjustments to the config file, you can start the docker container again. ```shell -docker start qbit_manage +docker start qbit-manage ``` -Either tail the log ( `tail -f "/opt/qbit_manage/activity.log"` ) or open the log file after a few minutes to check for any errors or behaviour that may have been unexpected. The container has been deliberately set to **DRY RUN MODE** initially so you can see what the script will do without actually moving deleting, tagging, or categorising anything.. Once you are happy your life's work will not be destroyed and any errors have been resolved you can edit the qbit_manage variables in the sandbox settings.yml file and then run the role again. Set `qbt_dry_run: false` to run in live mode. This will delete and move files according to your settings. +Either tail the log ( `tail -f "/opt/qbit-manage/activity.log"` ) or open the log file after a few minutes to check for any errors or behaviour that may have been unexpected. The container has been deliberately set to **DRY RUN MODE** initially so you can see what the script will do without actually moving deleting, tagging, or categorising anything.. Once you are happy your life's work will not be destroyed and any errors have been resolved you can edit the qbit_manage variables in the sandbox settings.yml file and then run the role again. Set `qbt_dry_run: false` to run in live mode. This will delete and move files according to your settings. Apply the changes to the sandbox settings file with: From c04913dfa05d6699c7c3f71733de6a6ee05ad78b Mon Sep 17 00:00:00 2001 From: Robert Simplicio Date: Tue, 26 Nov 2024 20:09:14 -0800 Subject: [PATCH 2/4] Update qbit-manage.md with missing logs directory in tail command The tail log command is missing the /logs/ directory --- docs/sandbox/apps/qbit-manage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sandbox/apps/qbit-manage.md b/docs/sandbox/apps/qbit-manage.md index 1b48b43bb..af785d3d0 100644 --- a/docs/sandbox/apps/qbit-manage.md +++ b/docs/sandbox/apps/qbit-manage.md @@ -71,7 +71,7 @@ After making adjustments to the config file, you can start the docker container docker start qbit-manage ``` -Either tail the log ( `tail -f "/opt/qbit-manage/activity.log"` ) or open the log file after a few minutes to check for any errors or behaviour that may have been unexpected. The container has been deliberately set to **DRY RUN MODE** initially so you can see what the script will do without actually moving deleting, tagging, or categorising anything.. Once you are happy your life's work will not be destroyed and any errors have been resolved you can edit the qbit_manage variables in the sandbox settings.yml file and then run the role again. Set `qbt_dry_run: false` to run in live mode. This will delete and move files according to your settings. +Either tail the log ( `tail -f "/opt/qbit-manage/logs/activity.log"` ) or open the log file after a few minutes to check for any errors or behaviour that may have been unexpected. The container has been deliberately set to **DRY RUN MODE** initially so you can see what the script will do without actually moving deleting, tagging, or categorising anything.. Once you are happy your life's work will not be destroyed and any errors have been resolved you can edit the qbit_manage variables in the sandbox settings.yml file and then run the role again. Set `qbt_dry_run: false` to run in live mode. This will delete and move files according to your settings. Apply the changes to the sandbox settings file with: From 89088e9f78512b136aca6239f74b12a1de83e82b Mon Sep 17 00:00:00 2001 From: salty Date: Sat, 30 Nov 2024 01:59:45 +0100 Subject: [PATCH 3/4] Update qbit-manage.md --- docs/sandbox/apps/qbit-manage.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/sandbox/apps/qbit-manage.md b/docs/sandbox/apps/qbit-manage.md index af785d3d0..670c9a671 100644 --- a/docs/sandbox/apps/qbit-manage.md +++ b/docs/sandbox/apps/qbit-manage.md @@ -1,12 +1,12 @@ -# qBit Management +# qBit Manage ## What is it? -[qBit Management](https://github.com/StuffAnThings/qbit_manage) is a program used to manage your qBittorrent instance. +[qBit Manage](https://github.com/StuffAnThings/qbit_manage) is a program used to manage your qBittorrent instance. | Details | | | | |-------------|-------------|-------------|-------------| -| [:material-home: qBit Management](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:octicons-link-16: Docs](https://github.com/StuffAnThings/qbit_manage/wiki){: .header-icons } | [:octicons-mark-github-16: Github](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:material-docker: Docker:](https://hotio.dev/containers/qbitmanage/){: .header-icons } | +| [:material-home: qBit Manage](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:octicons-link-16: Docs](https://github.com/StuffAnThings/qbit_manage/wiki){: .header-icons } | [:octicons-mark-github-16: Github](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:material-docker: Docker:](https://hotio.dev/containers/qbitmanage/){: .header-icons } | **Functions include:-**
@@ -33,7 +33,7 @@ ### 1. Installation -Before installing qBit Management, you should have a **[qBittorrent](../../apps/qbittorrent.md)** instance running on your local machine. +Before installing qBit Manage, you should have a **[qBittorrent](../../apps/qbittorrent.md)** instance running on your local machine. ``` shell @@ -105,4 +105,4 @@ qbit_manage: qbt_width: "100" # Default is "100" ``` -- [:octicons-link-16: Documentation: qBit Management Docs](https://github.com/StuffAnThings/qbit_manage/wiki){: .header-icons } +- [:octicons-link-16: Documentation: qBit Manage Docs](https://github.com/StuffAnThings/qbit_manage/wiki){: .header-icons } From fc217a4491f1b2e665c3d8bf3f3cc473f80beb6e Mon Sep 17 00:00:00 2001 From: salty Date: Sat, 30 Nov 2024 02:07:53 +0100 Subject: [PATCH 4/4] Update qbit-manage.md --- docs/sandbox/apps/qbit-manage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sandbox/apps/qbit-manage.md b/docs/sandbox/apps/qbit-manage.md index 670c9a671..0dd30bc58 100644 --- a/docs/sandbox/apps/qbit-manage.md +++ b/docs/sandbox/apps/qbit-manage.md @@ -8,7 +8,7 @@ |-------------|-------------|-------------|-------------| | [:material-home: qBit Manage](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:octicons-link-16: Docs](https://github.com/StuffAnThings/qbit_manage/wiki){: .header-icons } | [:octicons-mark-github-16: Github](https://github.com/StuffAnThings/qbit_manage){: .header-icons } | [:material-docker: Docker:](https://hotio.dev/containers/qbitmanage/){: .header-icons } | -**Functions include:-**
+**Functions include:**
- Tag torrents based on tracker and then set seed goals/limit upload speed by tag.