JudoChinX

GitHub Project: https://github.com/JudoChinX/rangarr Docker Hub: https://hub.docker.com/r/judochinx/rangarr Rangarr is a lightweight orchestration service that automates and staggers media searches (upgrades and missing) across multiple *arr instances (Radarr, Sonarr, Lidarr). It helps keep your library complete without overwhelming your indexers or API limits. Built as a direct response to recent security issues in the space, it has no telemetry, no external connections, no database, and no persistence layer. It communicates only with the *arr instances you configure. You can read the full threat model in the SECURITY.md file on the repo. Key Features: Multi-Instance Support: Manage Radarr, Sonarr, and Lidarr from a single service. Smart Staggering & Interleaving: Prevents "thundering herd" issues by spacing out search requests and balancing missing items with upgrades. Retry Logic: Intelligent skip windows for items recently searched. No UI/Dashboard: You monitor it via docker compose logs -f. I consider the lack of open ports a security feature. I'm a career Linux Systems Administrator and Automation Developer. I built this with the same rigor I'd use for a production enterprise environment: Distroless Container: Multi-stage build using python:3.13-slim (builder) and gcr.io/distroless/python3-debian13 (runtime). Zero Shell: No shell, no package manager, and no build tools in the final image. Non-Root: Runs as nonroot (UID 65532) with a read-only filesystem mount for config. Zero Ports: Rangarr is a daemon, not a web server. No open ports, no API, nothing to attack from the outside. Multi-Arch Support: Native images (<25MB) for both amd64 and arm64 (Raspberry Pi, etc.) pushed to Docker Hub. Automated Audit: The CI/CD pipeline runs Bandit, pip-audit, mypy, and Ruff on every build. If it's not green, it doesn't push. Docker Scout Enabled: Vulnerabilities? None found. Configuration Notes: The Unraid template by default relies on Environment Variables for a quick and easy setup. If you prefer to use a config.yaml file instead, simply map an Unraid appdata path to /app/config in the template and change the RANGARR_CONFIG_SOURCE variable to file. For complete setup instructions, architecture details, and how to format your configuration, please refer to the main README and User Guide on GitHub. Development Transparency: AI tooling was used to assist with development tasks in this project. The architecture—including the decision to use no database and no persistence layer—was designed entirely by the author. All code is strictly human-reviewed before inclusion. How to Request Support: Please use this thread for Unraid-specific setup questions, path mapping issues, or template troubleshooting. If you are running into issues, please provide: A brief description of the problem. The relevant section of your Unraid Docker log for Rangarr. Whether you are using the Environment Variable or config.yaml setup method. A fun note about the pig: This is Ranger, the pig. He's a truffle hunter who respects the environment and always leaves things better than he found them. A big thanks to my wife for drawing this up for me in a rush.