CLI Usage

The continuous scheduler lives in web.py. The CLI entry point, inspectarr.py, is for one-off scans and testing — it runs a single scan and exits.

---

Flags

python3 inspectarr.py                    # run a single scan, then exit
python3 inspectarr.py --config /path     # use an alternate config file
python3 inspectarr.py --dry-run          # force dry run regardless of config
python3 inspectarr.py --retry-now        # flush the retry queue first, then scan
python3 inspectarr.py --daemon           # continuous scan loop (poll_interval_seconds)

Flag	Effect
--config <path>	Load config from a non-default location
--dry-run	Override dry_run to true for this run — log matches, take no action
--retry-now	Process any due entries in the retry queue before running the scan
--daemon	Run a continuous scan loop instead of single-shot, with graceful SIGINT/SIGTERM handling. Also processes retries and quarantine timeouts each cycle, exactly as the web scheduler does.

---

Running a one-off scan in Docker

If Inspectarr is running as a container, you can run a single CLI scan against it without disturbing the daemon:

docker exec inspectarr python inspectarr.py --dry-run

---

When to use the CLI vs the web UI

• Web UI / scheduler — normal operation. Set it and forget it; the daemon scans on your interval.
• CLI — testing a config change, validating a new rule with --dry-run, or forcing a retry flush. Use --daemon for a headless continuous loop without the web UI.