Repository navigation
Home
Stop babysitting your torrents. qbt-rules is a client-server automation engine that watches qBittorrent and reacts to events, on a schedule, or on demand β categorizing, tagging, cleaning up, and re-prioritizing torrents so you don't have to.
- id: delete-well-seeded-torrents
meta:
description: "Delete well-seeded torrents automatically"
context: weekly-cleanup
conditions:
all:
- field: info.ratio
operator: ">="
value: 2.0
actions:
- type: delete_torrent
params:
delete_files: falseThat's a real, complete rule β no code, just YAML. A few things people actually use it for:
- π¬ Auto-categorize new downloads by name pattern the moment they're added
- π§Ή Clean up anything that's hit ratio/seeding-time targets, on whatever schedule you want
- π Block or quarantine unwanted file types before they finish downloading
- π Enforce ratio rules on private trackers without checking in manually
- β« Re-prioritize the queue when something urgent lands
One Docker container, one YAML file, and qBittorrent does the rest. Get started in 5 minutes β
- Introduction
- Quick Start
- Rules Architecture
- Contexts
- Conditions
- Available Fields
- Actions
- Reusable References
- HTTP API Reference
- CLI Reference
- Dashboard
- Metrics
- Security
- In-Depth Configuration
- Deployment
- Upgrading to 0.11
- Scheduling
- Examples
- Advanced Rules Example
- Advanced Topics
- Frequently Asked Questions
- Troubleshooting
- For Developers
- License
qbt-rules | A rules engine for qBittorrent automation, with a job queue, scheduler and web dashboard
GitHub β’ Container image β’ Releases β’ Issues β’ Discussions β’ Changelog β’ Contributing β’ License
Requirements: Docker β’ qBittorrent with Web UI enabled
Released into the public domain under the Unlicense
This wiki is generated from docs/wiki/ on every push to main: edits made here are overwritten. Change it with a pull request.
- Rules Architecture
- Contexts
- Conditions
- Actions
- Available Fields
- Reusable References
- HTTP API Reference
- CLI Reference
- Dashboard
- Metrics
- In-Depth Configuration
- Deployment
- Upgrading to 0.11
- Scheduling
- Examples
- Advanced Rules Example
- Advanced Topics
- π Client-server architecture (HTTP API + worker)
- π¦ Persistent job queue (SQLite or Redis)
- β»οΈ Reusable references (
$ref,${vars.x}) - π₯οΈ Web dashboard with a validating
rules.ymleditor - π³ Docker-first deployment