5 phút đọc
egg82/fetcharr: hunts for missing or upgradable media in your *arr stack – Repository egg82/fetcharr. Mô tả: hunts for missing or upgradable media in your *arr stack. 335 stars, 4 forks, ngôn ngữ chính Java, cập nhật 2026-08-17.
1. Repository làm gì?
Since Huntarr died, I still needed an application that scanned and upgraded my media. I tried a few different projects but I didn't like any of them for various reasons.
Since vibe-coding is a big deal these days, I decided to brush off my Java rust and try my hand at a containerized project that used configuration similar to Unpackerr and did one thing and did it well. The few portions with LLM assistance have been noted (search ChatGPT) and generated code was read and verified before use.
Note that LLM assistance is also used to find and report bugs (see: issues) and those are noted appropriately with a "Claude Code" line. The code is still hand-written and how each issue is resolved is still decided by me, a human.
tl;dr LLM-generated code is largely out of this repo by design. I wanted to write something by hand, but there's a balance between "I want to do it myself" and "this is a real thing used by people" so there's still a few instances in here. All properly noted/credited.
No use of opencode, claude code, cursor, etc in this project. Any LLM assistance was done via web UI. Largely to ask questions about design, errors, or specific details I've forgotten since touching Java. Readme also written by hand.
I think I hit that nail on the head.
2. Dữ liệu và cấu trúc đáng chú ý
Currently supports the following:
The Huntarr saga is an interesting one if you're curious, but if you're not familiar with the history then here's the short of what Fetcharr does:
The idea is that you’ll occasionally want to go through all your media and make sure it’s the best quality available and that nothing’s missing. New releases get published, remuxes sometimes fix issues, etc. This little CLI container goes through and periodically searches every *arr app you connect it to, so you don’t have to sacrifice hours of your weekend doing (as much) manual hunting.
Now, it's worth mentioning that Sonarr, Radarr, etc have had a built-in system that does this for a while now, but I've never gotten them to work reliably. Maybe it's just bad luck or some strange misconfiguration, but I've always had a need for apps like Scoutarr (Upgradinatorr), Huntarr, etc. Considering the popularity of these apps it feels like I am not the only one.
Update to this: I learned that at *arr stack uses RSS feeds to scan for and fetch updates, so if your indexer doesn't support those feeds or the feeds or too old (or a myriad of other issues that can come from this kind of system) then you won't get replacement content even if it exists. This is why these kinds of "hunting", "fetching", "upgrading", etc systems work so well. They simply force the *arr apps to periodically update their content through their configured indexer, regardless of RSS feed availability.
If the concept sounds interesting to you, give Fetcharr a try. See if it finds anything. If my experience while developing this is anything to go by, you'll get some results almost immediately. Likely within a few hours, and maybe even within a few seconds. See if it helps and if you want to add it to your stack.
Docker, Kubernetes, whatever container system you currently use. Use the latest tag for the latest production build or the dev tag for the latest development build.
3. Khả năng ứng dụng và giới hạn
Or by immutable tag: https://hub.docker.com/r/egg82/fetcharr/tags
Also available on GitHub: https://github.com/users/egg82/packages/container/package/fetcharr
Fetcharr runs as UID 1000 and GID 1000 by default. If you need to use a different user, you can do that in one of two ways:
The limitation of this method is that Fetcharr cannot (and will not attempt to) change volume ownership for any data directories you give it.
The second option is to let Fetcharr remap its user after starting the container as root:
The upside to this method is that Fetcharr will start as root and be able to modify volume mounts as needed. The downside is that this is inherently less secure, even though it will drop privileges almost immediately after starting.
Unraid uses 99:100 (nobody:users) so you'll want to use one of the above options. Put the flag in the Extra Parameters field of the container's template after switching to Advanced View.
With USE_FILE_CACHE set to "auto", Fetcharr will determine if the configured cache directory is writable. If so, it will enable use of file caching. If not, it will disable file caching.
With USE_MEMORY_CACHE set to "auto", Fetcharr will determine if the file cache is usable. If so, it will disable use of in-memory caching. If not, it will enable in-memory caching.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
