Remove Readarr #1206

Closed
opened 2026-02-04 23:39:27 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @nickheyer on GitHub (Jul 2, 2025).

Please verify that you have read and understood the guidelines.

yes

What type of issue is this?

Documentation

A clear and concise description of the issue.

The Readarr project has been archived as of the 27th (though mostly abandoned for some time now).
https://github.com/Readarr/Readarr
https://community-scripts.github.io/ProxmoxVE/scripts?id=readarr

Which browser are you using?

Other

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @nickheyer on GitHub (Jul 2, 2025). ### Please verify that you have read and understood the guidelines. yes ### What type of issue is this? Documentation ### A clear and concise description of the issue. The Readarr project has been archived as of the 27th (though mostly abandoned for some time now). https://github.com/Readarr/Readarr https://community-scripts.github.io/ProxmoxVE/scripts?id=readarr ### Which browser are you using? Other ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the website label 2026-02-04 23:39:27 +03:00
Author
Owner

@MickLesk commented on GitHub (Jul 2, 2025):

We know this, but archived != Working. We wanted to leave the script there for a maximum of six months for the transition. The question is whether we write an info as a note for the website or remove it from the website completely

@MickLesk commented on GitHub (Jul 2, 2025): We know this, but archived != Working. We wanted to leave the script there for a maximum of six months for the transition. The question is whether we write an info as a note for the website or remove it from the website completely
Author
Owner

@nickheyer commented on GitHub (Jul 2, 2025):

No worries sounds like you've got it handled, but also I would realistically say in its current state its basically unusable (there could be workarounds out there though).

@nickheyer commented on GitHub (Jul 2, 2025): No worries sounds like you've got it handled, but also I would realistically say in its current state its basically unusable (there could be workarounds out there though).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1206