Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR]: Declaration of different cache path maps in qbit mover script #710

Open
2 tasks
Konvett opened this issue Dec 17, 2024 · 0 comments
Open
2 tasks

[FR]: Declaration of different cache path maps in qbit mover script #710

Konvett opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
feature request New feature or request

Comments

@Konvett
Copy link

Konvett commented Dec 17, 2024

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

@Konvett Konvett added the feature request New feature or request label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants