tatoalo / torrentmanager Goto Github PK

Depending on the cleaning scheduling, there might be issues with respect to when a torrent is being removed before it was moved to its permanent save path.

This can be addressed in one of two ways:

• make educated guess on time elapsed from download complete and use that as a threshold (faster approach, less invasive)
• check if the save path contains the expected file (slower, requires mounting additional volume)

Currently, the default cleaner schedule reduces this possibility to a bare minimum, first option seems the way to go since I don't like exposing too much of the file system to the container itself.

Allow the cronjob to be more easily tweaked without fiddling with the container building process itself.

Once the download has been completed, the folder must be renamed as per convention and moved to one of the mapped target directories.

API

I've been looking for a feature to be able to set seedings limits to sepcific tags or trackers.

qBittorrent currently supports seeding limits for all torrents, or manually for individual ones.
It would be nice if torrentManager could apply those individual seeding limits based on tags or trackers.

Seeding limits i'm looking for that exist in qBittorrent:

• When ratio reaches X
• When seeding time reaches X

(this is how it looks in qbittorrent for all torrents)

use case here would be to automatically download new releases, tag them, seed them a specific time or until a ratio hits and then delete them (to increase ratio on a private tracker)

It would be nice to have some visibility on the metrics, it's not critical and #7 should address most of that need.
The main concern would be to understand communication issues with the instance, but the cron monitoring would already cover that area, let's see.

It would be rad to have some sort of remote logging feature set, basically I'm forcing my hand to use lnav 😄

Currently there's no way of understanding when a job has failed.

AC:

• Implement simple monitoring solution

Depending on the scheduling pattern, there might be issues of race condition on the data resource.

Any plans to publish this on docker hub directly?

Seems really cool, was looking excatly for that, will give it a try later on.

I'm asking for docker hub simply because for the system i would use it for (unraid), installing from docker hub is default.

The Cleaner component could be used to resolve discrepancies found between qBittorent state and the persistent dictionary component.

Add support for Python 3.11 🐍 🚀

A torrent that has been completely downloaded but somehow ends up in the 'stalled' status, will never get to the 'done' state.

It would be neat to have some support for trackers, namely:

• Put specific torrents with specific trackers under the same category/tag (depending on use case)

This may be extremely important with regards to private trackers.

AC:

• Update configuration with a specific section for trackers (and respective labelling)
• Add business logic