Un-deprecate requestrr using the forked version

[CLHatch]

Pull request

Purpose
Describe the problem or feature in addition to a link to the issues.

Approach
How does this change address the problem?

Open Questions and Pre-Merge TODOs
Check all boxes as they are completed

• Use github checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage
Links to blog posts, patterns, libraries or addons used to solve this problem

Requirements
Check all boxes as they are completed

• These changes meet the standards for contributing.
• I have read the code of conduct.

Summary by Sourcery

Re-enable and update the Requestrr app to use the maintained forked image and correct metadata.

Enhancements:

• Mark Requestrr as no longer deprecated and refresh its app metadata description.
• Adjust Requestrr container configuration, including environment and volume paths, to match the forked image requirements.
• Switch Requestrr Docker images for x86_64 and aarch64 to the forked repositories.

Documentation:

• Update Requestrr documentation links, badges, and description to point to the maintained fork and reflect expanded media support.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR re-enables the Requestrr app in DockSTARTer by switching documentation, labels, and compose templates from the deprecated LinuxServer image to the actively maintained thomst08 fork, updating metadata, image names, and configuration paths/ports accordingly.

File-Level Changes

Change	Details	Files
Update Requestrr documentation to point at the thomst08 fork and its Docker Hub/GitHub resources.	Change Docker Pulls badge to use the thomst08/requestrr Docker Hub repository. Change GitHub Stars badge to reference the thomst08/requestrr GitHub repository. Update the description line to link to the thomst08 Requestrr wiki and list supported services including Lidarr and Overseerr.	docs/apps/requestrr.md
Un-deprecate the Requestrr app and refresh its app metadata description.	Flip the deprecated label value from true to false for the Requestrr service. Replace the deprecated description advising to use Doplarr with a current description of Requestrr’s functionality. Preserve the nicename label unchanged.	.apps/requestrr/requestrr.labels.yml
Adjust Requestrr compose configuration to align with the thomst08 image’s expectations.	Add REQUESTRR_PORT environment variable with default value 4545 to the service environment. Change the config volume mapping from /config to /root/config in the container to match the forked image layout. Leave core runtime environment variables (PGID, PUID, TZ, restart policy, and host config root) intact.	.apps/requestrr/requestrr.yml
Switch architecture-specific images from LinuxServer to thomst08 fork images.	Change the aarch64 service image from lscr.io/linuxserver/requestrr to lthomst08/requestrr while preserving the tag variable. Change the x86_64 service image from lscr.io/linuxserver/requestrr to thomst08/requestrr while preserving the tag variable. Keep service naming and other compose keys unchanged.	.apps/requestrr/requestrr.aarch64.yml .apps/requestrr/requestrr.x86_64.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• The aarch64 image reference uses lthomst08/requestrr while the x86_64 and badges use thomst08/requestrr; please confirm and align the image name across architectures to avoid pulling from the wrong repo.
• You've changed the config volume from /config to /root/config and introduced REQUESTRR_PORT=4545; double-check that these align with the forked image's expected config path and port usage, and that they remain consistent with how other apps are configured in DockSTARTer.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The aarch64 image reference uses `lthomst08/requestrr` while the x86_64 and badges use `thomst08/requestrr`; please confirm and align the image name across architectures to avoid pulling from the wrong repo.
- You've changed the config volume from `/config` to `/root/config` and introduced `REQUESTRR_PORT=4545`; double-check that these align with the forked image's expected config path and port usage, and that they remain consistent with how other apps are configured in DockSTARTer.

## Individual Comments

### Comment 1
<location> `.apps/requestrr/requestrr.x86_64.yml:3` </location>
<code_context>
 services:
   requestrr<__instance>:
-    image: lscr.io/linuxserver/requestrr:${REQUESTRR<__INSTANCE>__TAG?}
+    image: thomst08/requestrr:${REQUESTRR<__INSTANCE>__TAG?}
</code_context>

<issue_to_address>
**issue (bug_risk):** Consider aligning the image repository between aarch64 and x86_64 definitions.

The aarch64 config uses `lthomst08/requestrr` while this uses `thomst08/requestrr`. If that’s not intentional, one arch may pull a different or non-existent image. Please standardize the namespace across architectures if they’re meant to be the same image.
</issue_to_address>

### Comment 2
<location> `.apps/requestrr/requestrr.yml:9` </location>
<code_context>
       - PGID=${PGID?}
       - PUID=${PUID?}
       - TZ=${TZ?}
+      - REQUESTRR_PORT=4545
     restart: ${REQUESTRR<__INSTANCE>__RESTART?}
     volumes:
</code_context>

<issue_to_address>
**suggestion:** Using a hardcoded port in the environment may reduce configurability.

Hardcoding `REQUESTRR_PORT=4545` limits flexibility if users want multiple instances or a different port. Consider exposing this as an env var (e.g. `${REQUESTRR<__INSTANCE>__PORT?}`) for consistency with the other settings, unless a fixed port is an intentional requirement.

Suggested implementation:

```
      - TZ=${TZ?}
      - REQUESTRR_PORT=${REQUESTRR<__INSTANCE>__PORT?}
    restart: ${REQUESTRR<__INSTANCE>__RESTART?}

```

1. Ensure that `REQUESTRR<__INSTANCE>__PORT` is defined in the corresponding environment (e.g. `.env` or the parent compose file) for each instance.
2. If there is documentation or example configuration for Requestrr, add `REQUESTRR<__INSTANCE>__PORT` to the documented variables with the default value `4545` to preserve the previous behavior as a suggested default.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): Consider aligning the image repository between aarch64 and x86_64 definitions.

The aarch64 config uses lthomst08/requestrr while this uses thomst08/requestrr. If that’s not intentional, one arch may pull a different or non-existent image. Please standardize the namespace across architectures if they’re meant to be the same image.

[sourcery-ai]

suggestion: Using a hardcoded port in the environment may reduce configurability.

Hardcoding REQUESTRR_PORT=4545 limits flexibility if users want multiple instances or a different port. Consider exposing this as an env var (e.g. ${REQUESTRR<__INSTANCE>__PORT?}) for consistency with the other settings, unless a fixed port is an intentional requirement.

Suggested implementation:

      - TZ=${TZ?}
      - REQUESTRR_PORT=${REQUESTRR<__INSTANCE>__PORT?}
    restart: ${REQUESTRR<__INSTANCE>__RESTART?}

1. Ensure that REQUESTRR<__INSTANCE>__PORT is defined in the corresponding environment (e.g. .env or the parent compose file) for each instance.
2. If there is documentation or example configuration for Requestrr, add REQUESTRR<__INSTANCE>__PORT to the documented variables with the default value 4545 to preserve the previous behavior as a suggested default.