Espressomatic

The unraid docker templates only support a single container and limbo is a stack of multiple containers. When unraid adds compose support and retools their templates then I’ll support that for sure. Right now I’ve put in configuration declarations to work with the compose manager plus.

I took that to heart and decided to do something about it. So yea, I fixed it so Lidarr doesn't need to use Lidarr's servers at all anymore. You can now query anything on MusicBrainz locally at insane speeds compared to Lidarr's remote server, plus access a couple of dozen artwork sources instead of the non-working ones the Lidarr devs had hardcoded into the app. Pause/stop/start Lidarr's scheduled tasks, theming engine added to Lidarr with over 30 themes, instantly remove unwanted media types like Tape or Vinyl and more soon: integrated direct downloader, split/custom releases... Works with this binhex Unraid docker or any lsio/hotio container on any platform. Supported with Compose Manager Plus on Unraid, docker compose on other systems. https://github.com/HVR88/Limbo

Installation instructions for Unraid now included on the repo: https://github.com/HVR88/Limbo

I now have the stack deploying top to bottom on Unraid using Compose Manager Plus. Install the Compose Manager Plus plugin Paste Limbo's compose.yaml into the first window, and example.env into the second Add your own personal MusicBrainz replication key (free from Metabrainz) to the env declaration at the top of the second window Save and Start You can monitor installation progress at HOST_IP:4808 While that's happening you can also install Limbo Stick (a helper sidecar) next to your Lidarr installation - it allows theming Lidarr, adds direct-download buttons to Lidarr and gives Limbo the ability to manage/control Lidarr's background tasks. This is still in beta and the Downloader isn't yet fully exposed in the UI, so you can't kick off Limbo-based downloads and imports.

There's a greater chance of growing a third leg out of my forehead than any USB thumb drive failing on use with Unraid. Haha. I posted that I didn't see a reason to boot from NVME or anything other than USB, but I remembered one (and only one). Every motherboard I've ever used has occasional issues booting from USB - doesn't matter if it was old BIOS or newer UEFI. It's happened on all systems here and there. On one ASROCK system if the machine has been down for a while, I have to move the USB drive to a different port for the board to see it - it doesn't matter the USB drive used. Restarting doesn't have that issue ever.

For sure. I hadn't seen a git hub link, but I'll go there as I'm sure I'll have a number of others to post.

I get that's the way it works now. What I'm suggesting is allowing the compose or a template to be added first, and that determines the project name. Like with Unraid's container-based template docker support. Or Portainer's templates.

One more when you get the chance... Don't let modals get longer than the viewport - controls are pushed beyond the visible display frame when I'm running on anything but my 32" display.

PLEASE (PLEASE!) can we have Compose Manager actually delete directories under /boot/config/plugins/compose.manager/projects/ when you delete a stack? If I see another stack get "003" in its name I'm going to lose it. I'd also like to be able to create stacks without setting their names or descriptions - my compose file already includes that information and it's not for the user to decide when I'm shipping a pre-made stack. I'd also like the ability to set compose and env via URL instead of pasting - including the ability to just paste a single GitHub URL to grab both at once. I'd also break with Unraid's convention of using the "DONE" button and relabel that button on the bring-up window "CANCEL" if you can't close the window without stopping the process. Anyone involved in Unraid web design: DONE does not mean what you think it means and CANCEL buttons shouldn't be named "DONE" all over the UI.

Themes in Lidarr:

It looks like it has great bones and could make the basis of a new Unraid release. It could definitely do with some UI/UX love, but I acknowledge that the current state is trying to shoehorn a lot of functionality into what the Unraid base webUI offers.

I think I'll have mastered all matters of cosmology and astro-physics before I understand the benefit of SSD boot/licensing on Unraid, but glad some people are getting a kick out of it. Now... when the time comes for a brand new docker UI with full compose and multi-container support... then I'll be smashing plates and yelling from the rooftops.

No issue, LXC working fantastic. Just had a couple of ideas I wanted to run by you that I don't want to post in the forum.

I tried sending you a message here on the forum - it failed. Wanted to send some info in private if you can look into that.

"I updated to Unraid 7.2.4 and all I got was this 7.2.4 version tag" When does version 8 come out? ;)

Right now working on a downloader and importer that will sit outside Lidarr (yay! no plugins nothing to add to lidarr). So far so good, much better than any other downloader I've tried.

I hope to move to a responsive webUI when it's feature-complete at version 2.0, in the meantime I'm having fun playing with this decidedly non-mobile-friendly design. :) Providers configuration: enable/disable, api keys, logins, etc. Manual bulk artist/release refresh with realtime ID to name resolution on paste:

Not yet. The project is going through a lot of change and I want to get all the base features in place first. At the same time I'm hoping that Unraid will deploy support for Compose-style multi-service templates soon, as the easiest way to deploy this is with my full stack release which includes a MusicBrainz server. Installing a-la-carte requires a lot more work: Lidarr, slskd, MusicBrainz and Limbo-Bridge

I'm thinking of pulling some of the RAM from a few servers and reselling it to buy a MacLarren.

The thought of a Best-buy NORMIE trying to wrap their heads around the concept of Unraid, let alone booting it and doing anything (at all) without SERIOUS hand-holding is enough to melt my brain. A lot of people out there will have the capability to do it. But the convincing they'll need, to believe it, is an almost insurmountable obstacle in and of itself. Then there are the other 90% who would have NO CLUE. Do you even know how many people out there can't change a light switch or a ceiling lamp? Or how many people don't know you can copy / paste using CTRL-C and V? That's like 95% of computer users. Brings me to a side-quest (point). A lot of people worried about AI. No need to worry. If you already know something, you can effectively use AI. If you don't, good luck. Those people aren't going to be able to use AI to replace anyone else. If you don't already know how to program, TRUST ME, you're not going to accomplish anything useful no matter how much AI you try to use to replace your lack of knowledge.

Adding a small plugin-like system to the bridge which will allow hooking either before metadata queries or after. This allows manipulation of the JSON returned to lidarr, manipulating the queries, issuing queries to any number of other tables or databases, combining metadata sources, etc. Super simple example: remove Vinyl release issues when there's anything else available.

To fix Lidarr's broken metadata search and significantly increase artist/album searches and additions, run your own MusicBrainz mirror and Lidarr metadata server. You can now test/deploy a full MusicBrainz stack using Compose Manager with no manual setup steps: https://github.com/HVR88/Limbo Over 30 Themes for Lidarr, with theme selection menus Block certain types of releases, like Vinyl, Tape, etc. Pause, restart or cancel Lidarr tasks on the fly Direct download buttons added into Lidarr UI Detailed Lidarr stats Artist refreshing Support for dozens of artwork and lyrics providers with your own custom priority/precedence settings Manual / Auto Downloader and Importer integrated soon (final testing) Needs ~300GB of storage space and 2-4 hours installation time (400-500GB recommended for future growth of the DB). A new thread will show up soon once I've finished writing Unraid-tailored instructions.

You can now test/deploy a full MusicBrainz stack using Compose: MusicBrainz Mirror Server PLUS - Full stack with Lidarr API Bridge Needs ~300GB of storage space and 2-4 hours installation time (400-500GB recommended for future growth of the DB). A new thread will show up soon once I've finished writing Unraid-tailored instructions.

I haven't looked at this in a long time, but I run it on a regular schedule for all 4 of my current servers. What version of Unassigned Devices do you have installed? The condition that creates that error is pretty straight forward, the script is looking for duplicate keys in your cfg, which indicates some invalid content. If you can post your cfg it should be easy to identify the problem.