Skip to content

Releases: ckcr4lyf/qbit-race

v2.0.0-alpha.8

26 May 07:05
1d6c722
Compare
Choose a tag to compare
v2.0.0-alpha.8 Pre-release
Pre-release

Bug Fixes

  • Use correct HTTP method to login (#33)

v2.0.0-alpha.4

08 Sep 14:09
1fe556a
Compare
Choose a tag to compare
v2.0.0-alpha.4 Pre-release
Pre-release

Can now install from npm: https://www.npmjs.com/package/qbit-race/v/2.0.0-alpha.4

Run qbit-race once to create config in ~/.config/qbit-race/ , set it up, and then the add would be (for autoDL):

Command: <complete path to qbit-race binary> (Can run which qbit-race to find it)
Arguments: add -p "(TorrentPathName)"

Example:

image

The post completion command in qbittorrent would be:

<complete path to qbit-race binary> completed -i "%I"

Example:

image

v1.1.0

03 Aug 13:38
d7c1032
Compare
Choose a tag to compare

Changes

  • Added support for autobrr

Installation

Please either clone from the tag:

git clone https://github.com/ckcr4lyf/qbit-race.git --branch v1.1.0

Or download the repository and unzip. Instructions remain same as v1.0.0 otherwise (see https://github.com/ckcr4lyf/qbit-race/releases/tag/v1.0.0)

1.0.0 - Stable Non-ESM Version

02 Feb 07:51
24cf7eb
Compare
Choose a tag to compare

Making an official release to "version lock" with existing scripts / guides on how to setup qbit-race

Going forward, qbit-race will switch to ESM mode, which will require changing the settings.js file (breaking change)

Download the repo as a zip and extract, then you can follow the instructions in the README in the unzipped repository to setup (since on master it will be changed for setup of a newer version.

Copied for your reference:

npm install
cp sample.env .env
cp sample.settings.js settings.js

Now open .env in an editor like nano or such, and change the values as per your setup. QBIT_PORT is the port the Web UI is listening on, NOT the port for incoming BitTorrent connections. DISCORD_WEBHOOK is optional, you should replace it with your chanell's webhook URL if you enable Discord noticiations in settings.js (more info below)

Once you think you've done it correctly, Validate it by running

npm run validate

If all went well, you'll see something like

2020-09-27T12:40:10.541Z [CONFIG] - Loaded .env
2020-09-27T12:40:10.644Z [CONFIG] - Updated COOKIE!
2020-09-27T12:40:10.656Z [AUTH] - Login completed in 0.07 seconds.
2020-09-27T12:40:10.656Z [TEST] - SUCCESS!