Instruction 06-prowlarr-installation-and-indexer-management: Reading

Prowlarr separates indexer management from the applications that consume indexer results. Without a central manager, an administrator may define the same endpoint, credentials, categories, and limits independently in several applications. That duplication increases configuration drift and makes credential rotation or endpoint changes harder. Prowlarr provides one administrative location for indexer definitions and can synchronize supported definitions to connected applications. It can also perform searches through its own interface, but it does not replace an automation application or a download client.

An indexer test is more than a simple check that a TCP port answers. Prowlarr may request the indexer's capabilities, verify the expected XML structure, test authentication, and compare the response with the configured implementation. A reachable endpoint can therefore still fail because its certificate is invalid, its API key is rejected, its URL base is wrong, the selected definition expects another protocol, or its response omits required fields. Categories matter as well: a search source may be healthy while returning no useful results because the selected categories do not overlap the categories requested by an application.

This lab deliberately uses a local Torznab-compatible teaching service. It returns synthetic metadata and never contacts a public content indexer. That design makes protocol behavior observable while avoiding dependence on third-party availability, accounts, rate limits, or content. Prowlarr is installed from an official GitHub release asset selected for the host architecture. The release API response and a locally calculated SHA-256 digest are retained in the workspace. A local digest detects later changes to the downloaded file, but it does not independently prove publisher authenticity unless it is compared with a trusted publisher-provided value or signature.

Prowlarr's state is as important as its executable. The launcher supplies an explicit data directory and redirects home, cache, configuration, temporary, and .NET CLI paths into /opt/lab-classroom/class54/. This supports repeatable rollback and prevents the exercise from intentionally writing configuration into the learner's normal home directory. In production, Prowlarr should run as a dedicated, minimally privileged service account, use protected credentials, have dependable backups of its application data, and be exposed only through an authenticated administrative path. Indexer use must comply with applicable law, provider terms, and organizational policy.