Add example Lidarr Connect script

[montchr]

Would a Lidarr setup example be worth adding to the settings page alongside the examples for Transmission and Deluge?

I've been working on getting Lidarr to send new imports to Betanin. It's been a long road, but I've got a basic workflow going in my environment. While I'm running my fork with the changes proposed in #34, I think a Lidarr script would work even without those changes.

The two Reddit discussions linked below have been really helpful getting this set up. They're tailored for calling beet import in the post-import script, but can be adjusted to work with Betanin.

https://www.reddit.com/r/Lidarr/comments/c1enh9/beets_lidarr/ https://www.reddit.com/r/Lidarr/comments/i4844t/anyone_got_a_working_lidarrbeets_workflow/

[w1ldg00se]

@montchr: Are there any advantages of using Lidarr instead of the download client to send the import request to betanin? Because i also use Lidarr but i would have never thought to use it for sending the import request to betanin, instead i use my download client sabnzbd to send the import request to betanin. For sabnzbd it's the same as for deluge, just $3 instead of $2.

[samcro1967]

@montchr I like the idea of a Lidarr script. I am using the LSIO Lidarr image and have beets installed via a mod into the image. I then call beets on import. It works well except when there is not a match, then it imports without processing. Would be ideal to put this in the middle of that workflow so an alert could be generated when intervention is required and wait for action to be taken. I think it makes more sense to do his from Lidarr so that it works with any download client and separate scripts are not required.

I may take a stab at putting betanin in the Lidarr image. Do you have a Lidarr import script for betanin that you have been testing you can share?