Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sailing:lidarr [2023/12/04 17:44] – [DeeMon] willy | sailing:lidarr [2024/02/27 12:17] (current) – removed willy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Prev to: [[sailing: | ||
| - | |||
| - | Next to: [[sailing: | ||
| - | ---- | ||
| - | ====== Lidarr the music organizer ====== | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | You will need Lidarr if you plan to organize and enrich your music collection. As a bonus point, i will show you how to use [[https:// | ||
| - | |||
| - | ===== Installation ===== | ||
| - | |||
| - | Lidarr is easily installed and managed within Gentoo linux since there is an ebuild for it. All you need to do is unmask it (at the time of writing this it's are masked for AMD64 at least): | ||
| - | <code bash> | ||
| - | > echo www-apps/ | ||
| - | </ | ||
| - | |||
| - | then install it: | ||
| - | <code bash> | ||
| - | > emerge -v lidarr | ||
| - | </ | ||
| - | |||
| - | This step will create a dedicated //lidarr// user but you will want to add it to the group //media//, that you have created before, so that the it will be able to access and manage your media collection: | ||
| - | <code bash> | ||
| - | > usermod -a -G media lidarr | ||
| - | </ | ||
| - | |||
| - | Also, you want to move Lidarr home folder under **/ | ||
| - | <code bash> | ||
| - | > usermod -m -d / | ||
| - | </ | ||
| - | |||
| - | |||
| - | ===== Reverse-Proxy configuration ===== | ||
| - | |||
| - | Before you proceed, you should make Lidarr accessible via the reverse-proxy, | ||
| - | <file txt lidarr.conf> | ||
| - | # Lidarr - Music | ||
| - | location ^~ /lidarr { | ||
| - | proxy_pass http:// | ||
| - | proxy_set_header Host $host; | ||
| - | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; | ||
| - | proxy_set_header X-Forwarded-Host $host; | ||
| - | proxy_set_header X-Forwarded-Proto $scheme; | ||
| - | proxy_redirect off; | ||
| - | proxy_http_version 1.1; | ||
| - | proxy_set_header Upgrade $http_upgrade; | ||
| - | proxy_set_header Connection $http_connection; | ||
| - | } | ||
| - | # Allow the API External Access via NGINX | ||
| - | location ~ /lidarr/api { | ||
| - | auth_basic off; | ||
| - | proxy_pass http:// | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | Add this to your **/ | ||
| - | < | ||
| - | include " | ||
| - | </ | ||
| - | |||
| - | and restart nginx: | ||
| - | <code bash> | ||
| - | > / | ||
| - | </ | ||
| - | |||
| - | ===== Startup ===== | ||
| - | |||
| - | There are some configuration that must be perform before actually starting the service. You need to briefly start and stop it to let it create the main configuration file, this is required because you need to generate a new API key: | ||
| - | <code bash> | ||
| - | > / | ||
| - | > / | ||
| - | </ | ||
| - | |||
| - | Now edit the newly created xml config file **/ | ||
| - | < | ||
| - | < | ||
| - | < | ||
| - | < | ||
| - | < | ||
| - | </ | ||
| - | |||
| - | Add Radarr to default runlevel, for autostart on reboot, and start it manually now: | ||
| - | <code bash> | ||
| - | > rc-update add lidarr default | ||
| - | > / | ||
| - | </ | ||
| - | |||
| - | Lidarr will now be accessible as **http:// | ||
| - | |||
| - | All set! Lidarr is running. | ||
| - | |||
| - | ===== Prowlarr link ===== | ||
| - | |||
| - | In order for Lidarr to benefit from Prowlarr automatic indexers management you need to open **http:// | ||
| - | go to // | ||
| - | * Lidar server: http:// | ||
| - | * API Key: grab it from Lidarr // | ||
| - | |||
| - | Then go to the Prowlarr indexers page and click on the // | ||
| - | |||
| - | ===== Usage ===== | ||
| - | |||
| - | Before you can actually use Lidarr you need to perform some initial setup in // | ||
| - | * Add a new Root Folder. Use **/ | ||
| - | |||
| - | Now enable " | ||
| - | * Thick "Set permissions" | ||
| - | * Set "chmod folder" | ||
| - | * set "chmod Group" to " | ||
| - | * save and restart the daemon (from the user icon on top-right corner) | ||
| - | |||
| - | you can fine tune and configure many other aspects of Lidarr as you wish. A very common guide is [[https:// | ||
| - | |||
| - | Please note that you will not yet be able to use Lidarr fully as you have not yet installed any downloader. | ||
| - | |||
| - | ===== DeeMon ===== | ||
| - | |||
| - | Lidarr is nice and good, but there is a very fast and practical way to start populating your music collection quickly, which is download 128Kb/sec MP3 files from a free [[https:// | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | In my experience, find music can be hard on the other ways, so this the best workaround i could come up with. I like that there is no need for another daemon, a Docker image or some other over complicated solution. DeeMon uses DeeMix internally to access your own Dezeer account and get the authors, albums or tracks you want. It's simple, it's easy, it's command-line based, and then Lidarr can easily pick it up from there and upgrade the tracks to FLAC when it finds them on you other indexers, but meanwhile you can quickly fill up your collection in a breeze. At this time i still haven' | ||
| - | |||
| - | DeeMon can do much more, check the online documentation, | ||
| - | |||
| - | You need to install manually DeeMon since it's not packaged for Gentoo, but it's really very easy. You want to create a DeeMon user, with it's default group the media group, so that any downloaded file will be created belonging to it for ease of access and management of the other apps: | ||
| - | |||
| - | <code bash> | ||
| - | > useradd -d / | ||
| - | </ | ||
| - | |||
| - | as usual, you put it in the daemons folder for consistency. Installing it it's easily done with **pip** but using pip directly is discouraged on Gentoo because it can severy break your system. To use pip on Gentoo you need to explicitly enable it for the //deemon// user by creating the file **/ | ||
| - | <file txt pip.conf> | ||
| - | [global] | ||
| - | break-system-packages = true | ||
| - | user = true | ||
| - | </ | ||
| - | |||
| - | You need to do two things now: | ||
| - | * set deemon umask to 0002 so that all files downloaded will be writable by Lidarr | ||
| - | * add **~/ | ||
| - | |||
| - | So, edit your **/ | ||
| - | <code bash> | ||
| - | export PATH=$PATH:/ | ||
| - | umask 0002 | ||
| - | </ | ||
| - | |||
| - | Installing DeeMon itself now it's pretty easy, but you need to become user //deemon// first: | ||
| - | <code bash> | ||
| - | > su - deemon | ||
| - | > pip install deemon | ||
| - | > deemon refresh | ||
| - | </ | ||
| - | |||
| - | Running the refresh command is required to have DeeMon autogenerate empty configuration files that you need to edit to match DeeMon file naming scheme to match Lidarr one, and perform some extra configuration like the **arl** cookie from Deezer. | ||
| - | |||
| - | In order for DeeMon to work it requires the **arl** cookie from Deezer. Grabbing the cookie is not difficult but it's an operation that you might have to do again every few months, as it will expire: | ||
| - | * Open the [[https:// | ||
| - | * Login with your Deezer account (or register a new account) | ||
| - | * Open the browser developer console (usually //CTRL+i// YMMV) | ||
| - | * Locate the cookies (under storage / cookies usually, YMMV) | ||
| - | * Copy the string associated to the **arl** cookie. | ||
| - | * | ||
| - | Edit the file **/ | ||
| - | < | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | }, | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | }, | ||
| - | </ | ||
| - | In the same config file, locate the // | ||
| - | |||
| - | In order for Lidarr to properly (and with less fuss) detect and import all the albums and tracks you need to edit the DeeMix preferences because by default the downloaded tracks will have a slightly different naming scheme than Lidarr. Now, you could also change Lidarr naming scheme if you prefer, but i think it's more reasonable to fix DeeMix because Lidarr defaults just works for Jellyfin. To do so, edit the file **/ | ||
| - | |||
| - | You will need to adjust a few lines, the following seems to be working fine for me: | ||
| - | < | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | </ | ||
| - | (note that i have copied only the relevant lines, do not modify the others unless you know what you want to do) | ||
| - | |||
| - | This is actually all... To use it, just type as user //deemon//: | ||
| - | |||
| - | <code bash> | ||
| - | > deemon download some_thing | ||
| - | </ | ||
| - | |||
| - | where some_thing is an artist or an album or a Dezeer ID.... and it will directly be downloaded inside your music library to enjoy! | ||
| - | |||
| - | As you can see DeeMon is not really integrated with Lidarr. All you do is actually download music in the same music collection as Lidarr. If you want to allow Lidarr to automatically upgrade your music quality, head to Lidarr GUI and, using the " | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | Now, head on to install the other services... | ||
| - | |||
| - | |||
| - | ---- | ||
| - | Next to: [[sailing: | ||
| - | |||
| - | Prev to: [[sailing: | ||