https://github.com/egg82/fetcharr
Disclaimer: I am the developer
Long story short, after Huntarr exploded I still wanted an app that did the core of Huntarr's job: find and fetch missing or upgradable media. I looked around for some solutions but didn't like them for various reasons. So, I made my own.
No web UI, configured via environment variables in a similar manner to Unpackerr. It does one job and it does it (a little too) well. Even when trying a few different solutions for a few days each, Fetcharr caught a bunch of stuff they all missed almost immediately. This is likely due to the way it weights media for search.
Since you made it this far, a few notes:
- I did still use ChatGPT on a couple of occasions. They're documented and entirely web UI - no agents. Anything it gave me was vetted and noted in the code before publishing.
- The current icon is temporary and LLM-generated. I've put out some feelers to pay an artist to create an icon. Waiting to hear back.
- It's written in Java because that's the language I'm most familiar with. SSL certs in Java containers can be painful but I added some code to make it as easy as Python requests or Node
- While it still has a skip-if-tagged-with-X feature, it doesn't create or apply any tags. I didn't find that portion necessary, despite other popular *arrs using it. Not sure why they do, even after developing this.
- Caution is advised when first using it on a large media collection. It'll very likely pick up quite a number of things initially if you weren't on top of things beforehand. Just make sure your pipeline is set up well, or you limit the number of searches or lengthen the amount of time between searches using the environment variables.
They do, but only by passively monitoring RSS feeds for new content that exceeds your current quality. They don't do active upgrade searches unless you manually trigger them.
The distinction is important if you imported some or all of your media library, rather than building it from scratch with the arr stack stuff. It also matters if you source some your content via providers that don't have RSS feeds.
I think you may have nailed what's happening to my stack. I remember looking into it a couple years ago and RSS was stuck in my head but I wasn't sure why. This tracks, and explains why active fetching works significantly better for me.