qbit_manage
qbit_manage copied to clipboard
StuffAnThings
[FR]: Declaration of different cache path maps in qbit mover script
Is your feature request related to a problem? Please elaborate.
My qbit Torrents container path is different from my host path. While the host is /mnt/user/**media_server**/torrents, my container path is /**data**/torrents. When I run the qbitmover script with --cache-mount "/mnt/cache", it doesn't pause any torrents because obviously it can't see /mnt/cache/**data**/torrents since it doesnt' exist. Thus I have to remap my container to match in order to get it to see the torrents in cache and pause them.
Describe the solution you'd like
I'd like to be able to declare the full cache path for torrents instead of just the cache mount point. This would enable you to set your container path to whatever you'd like.
Does your solution involve any of the following?
- [ ] New config option
- [ ] New command option
Describe alternatives you've considered
I've considered remapping my paths in all of my containers but I think it would be easier for most users (who may want to map their host and container paths differently) to be able to declare it in the script.
Who will this benefit?
Anyone whose host paths and container paths don't match.
Additional Information
No response
You shouldn't need to remap anything in your container since the script is meant to be run outside the container via userscripts. Did you follow Trash's guide in setting up the mover script?
This is what I was told in the #qbit-manage support channel in the Notifiarr Discord: https://paste.konvett.com/ZUbO7/qUtEmUnO71.png/raw
That's why I thought I needed to redo the mapping. I'm not using /data/ as my share name. But otherwise, I have followed TRaSH's guide for the setup, yes.
If I run it that way, the cache-mount feature doesn't work. It never sees the cache and so it never pauses anything in qbit.
I am using the prescribed paths from the guide directly, /data/torrents, and it is not pausing anything for me either, so I don't think this is a configuration issue.
