-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Readarr integration #99
Comments
Why not. But instead of tying this kind of feature to a specific app, I would prefer make it a general "hooks" system. |
That sounds a lot better yeah 👍 Readarr has an API https://readarr.com/docs/api/ Authentication is done via an API key the user can view in the settings. So you'd need to store that within Jelu somewhere secure so Readarr and Jelu can talk to each other. To give an overview of the process from the GUI on my readarr:
I believe you can do all this via the API and maybe cut out a couple of these steps (e.g. maybe you can search for and download a book directly without having to add the author first) |
Ok, I'll need to look at the API, it sounds a bit involved to just be a simple hook call. |
Upvoting this because Jelu is seriously the closest any service comes, and it's a huge gap in the community. It's so weird that it hasn't been filled yet. It would be awesome if you were the first. |
There is also lazylibrarian but readarr would be preferred. |
Might be out of scope for the project so feel free to close if it's a bit off topic.
It would be useful if there was functionality implemented that connected a user's readarr instance to Jelu. The result could be something like Overseerr or Jellyseerr that will automatically start downloads for books on a user's read list if it's setup.
The flow could be something like:
Currently, nothing like this appears to exist for ebooks, so it would be filling a hole in the self hosting community. However, it's probably a non-trivial feature to implement.
Happy to provide more context if needs be.
The text was updated successfully, but these errors were encountered: