You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: