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

[HELP] What is the minimum in the docker compose file to use this if using qbitorrent #64

Open
4 tasks done
dasb00ter opened this issue Feb 18, 2025 · 6 comments
Open
4 tasks done
Labels
question Further information is requested

Comments

@dasb00ter
Copy link

dasb00ter commented Feb 18, 2025

Before submitting a help request, I have:

  • Reviewed the documentation.
  • Ensured I am using ghcr.io/flmorg/cleanuperr docker repository.
  • Ensured I am using the latest version.
  • Enabled debug logging.

How can we help?

To me a novice the docker compose is fairly long. If I am running qbittorrent with a blocklist already in place it seems I can possibly skip some of the other options? Is that correct. As an example do I need to add the ARR parts of the docker compose...or will cleanuperr take care of it right in qbittorrent. I might have to read the documentation a few more times or wait for a tutorial lol

@dasb00ter dasb00ter added the question Further information is requested label Feb 18, 2025
@Flaminel
Copy link
Contributor

The Setup section describes how to use it if you're using qbit's blocklist. You don't need the content blocker, so don't enable that. And as for other settings, be sure to read on what they do and enable or disable them depending on your needs.

The example docker compose file is there to show all settings that can be configured.

@dasb00ter
Copy link
Author

Ok after reading "slower" I think I have consolidated my question. It seems that cleanuperr requires access to the ARRs API to do things like clean the ARR queue, blacklist in the ARR and research. Is that correct? There is a variable for each of the ARRs for blocklist path? If I'm using qbitorrent with it's blocklist for file types I'm not going to use content blocker. What would the path for the blocklist be? Is there a blocklist in the config files for the ARRs? Or is it the one you make with content blocker(which I'm not using). Sorry if I'm missing something or not fully understanding the workflow.

@Flaminel
Copy link
Contributor

No worries! We'll figure this out together.

It seems that cleanuperr requires access to the ARRs API to do things like clean the ARR queue, blacklist in the ARR and research. Is that correct?

Correct.

There is a variable for each of the ARRs for blocklist path? If I'm using qbitorrent with it's blocklist for file types I'm not going to use content blocker. What would the path for the blocklist be? Is there a blocklist in the config files for the ARRs? Or is it the one you make with content blocker(which I'm not using)

The path should be empty. As long as you don't enable the content blocker, those variables are not used. Those are just for specifying the blocklist for when cleanuperr needs to block files.

And by the way, if you have suggestions regarding the docs and how to make them more clear and easy to follow, please do tell me! Every bit helps!

@dasb00ter
Copy link
Author

dasb00ter commented Feb 19, 2025

I think you have thoroughly thought out application and as such have included allot of options. You have documented all of the options. I think it's hard to know how people will interpret them. Take me for example.

I've have read the how it works a couple of times albeit not all at once(life right!).

I feel fortunate that I'm using qbitorrent with it's blocklist option since you have put some time in to make it easier for those users. I'm just not sure what it is saving me in the workflow.

I see allot of things are disabled by default(and rightly so). I'm wondering does it make sense to enable for instance download removal.

Scenario. Sonarr finds what it thinks it's a suitable DL. It adds it to qbitorrent. Qbitorrent see s that the content is on the blacklist so it just it immediately marks as completed. It sits there in qbitorrent. Sonarr see s it's done but there is no suitable file for transfer. Whole process grinds to a halt. Queue cleaner comes along and see s that this file is in the qbitorrent blacklist and it talks to sonarr. It removes that particular file from sonarrs queue. It has sonarr place the file in sonarr s own internal black list and requests another search for a file. Another download should appear hopefully a real one. Eventually the user will have a good look at delete download options and have the 0 byte or unsuitable file removed automatically.

@Flaminel
Copy link
Contributor

The scenario you described is exactly how it works and it's what I'm using (I'm also using qBittorrent).

So it all comes down to what features you want enabled. If you only want to remove malicious files, queue cleaner and import failed variables should be all you need feature-wise. But be sure to also set up the arrs variables and also the qBittorrent url, user and pass. That way cleanuperr can actually check if the files have been blocked by qBittorrent.

@Flaminel
Copy link
Contributor

Did you succeed in configuring the app? Do you still need help with it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants