[FEATURE] Multiple "ignored root directory" entries #62

New Issue

giteasync · 2025-10-09T16:57:21-05:00

giteasync commented

2025-10-09 16:57:21 -05:00

Originally created by @Unspec7 on GitHub.

What would you like to see implemented next?

I currently have both cross-seed set up, and uploads via Audionut's Upload Assistant. All of my uploads are placed into their own directory, and are essentially treated the same as cross-seeds. It would be nice if we got an option at add multiple ignored root directories, similar to how we can add multiple unlinked categories.

Would also be nice to see the unlinked download setting moved to the download client setup, so we can create per-client configs for unlink detection, rather than a global setting.

Originally created by @Unspec7 on GitHub. ### What would you like to see implemented next? I currently have both cross-seed set up, and uploads via Audionut's Upload Assistant. All of my uploads are placed into their own directory, and are essentially treated the same as cross-seeds. It would be nice if we got an option at add multiple ignored root directories, similar to how we can add multiple unlinked categories. Would also be nice to see the unlinked download setting moved to the download client setup, so we can create per-client configs for unlink detection, rather than a global setting.

giteasync added the

enhancement

label 2025-10-09 16:57:21 -05:00

giteasync commented

2025-10-09 16:57:21 -05:00

@Flaminel commented on GitHub:

Sure, but I'm trying to understand why the global setting is not desired in this situation.

@Flaminel commented on GitHub: Sure, but I'm trying to understand why the global setting is not desired in this situation.

giteasync commented

2025-10-09 16:57:22 -05:00

@Unspec7 commented on GitHub:

I use different categories per client

@Unspec7 commented on GitHub: I use different categories per client

giteasync commented

2025-10-09 16:57:22 -05:00

@Unspec7 commented on GitHub:

The two paths that are to be treated as cross-seeds:

/common/path/uploads

/common/path/cross-seed

And then there are other, normal directories:

/common/path/movies

/common/path/tv
etc

@Unspec7 commented on GitHub: The two paths that are to be treated as cross-seeds: /common/path/uploads /common/path/cross-seed And then there are other, normal directories: /common/path/movies /common/path/tv etc

giteasync commented

2025-10-09 16:57:22 -05:00

@Flaminel commented on GitHub:

Would also be nice to see the unlinked download setting moved to the download client setup, so we can create per-client configs for unlink detection, rather than a global setting.

Please create a different feature request for that. Is there a scenario where you would have the same category in all your download clients but only want to clean it in some of them?

@Flaminel commented on GitHub: > Would also be nice to see the unlinked download setting moved to the download client setup, so we can create per-client configs for unlink detection, rather than a global setting. Please create a different feature request for that. Is there a scenario where you would have the same category in all your download clients but only want to clean it in some of them?

giteasync referenced this issue

2025-10-09 17:00:38 -05:00

[PR #62] [MERGED] Improve Transmission category detection #273

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Cleanuparr-Cleanuparr#62