[FR]: Allow multiple `root_dir`s

[TheColorman]

Is your feature request related to a problem? Please elaborate.

I have automatic torrent management that saves torrents to different folders based on several rules. Some of these folders are on different physical hard drives and have no common ancestor path (e.g. qBittorrent saves files to /A/categoryX, /A/categoryY, /B, etc. within its own container.

In short, this means I don't have a single "root dir" that houses all of my torrent files.

Describe the solution you'd like

Being able to specify multiple root dirs would alleviate this problem, allowing me to specify /A and /B as root dirs within the qbit_manage container.

Does your solution involve any of the following?

• [ ] New config option
• [ ] New command option

Describe alternatives you've considered

I believe I could probably run several instances of qbit_manage, each with a different root dir, but that's not an ideal solution

Who will this benefit?

Anyone with slightly abnormal torrent setups, which I have to imagine is not an insignificant share of users.

Additional Information

No response

[SawkeeReemo]

For what it's worth, I have a similar setup with one instance of qBT. But I have no problem having categories with paths outside of the root_dir. I just use absolute paths for all my categories, and that seems to do the trick.

Also, if you really need multiple root_dir support, couldn't you just do multiple qbm configs? One with each root_dir? You'd just have to be really organized, I think. But for instance, I only have one qbm container, but I have four config files for different purposes/qBT containers.

I have an environmental variable for qbm like this: QBT_CONFIG=config_*.yml

Then when it runs, it will find every config_*.yml file (config_vid.yml, config_misc.yml, etc) and load them sequentially.