0fflineuser

As Music Assistant supports subsonic (https://www.music-assistant.io/music-providers/subsonic/) and Navidrome expose a subsonic endpoint it should be possible (https://www.navidrome.org/docs/developers/subsonic-api/).

And it seems to have been merged so the plugin branch is not needed anymore, see: https://github.com/Lidarr/Lidarr/pull/1829

So the official image would work.

edit:

I just migrated and I can confirm it works.

I used lscr.io/linuxserver/lidarr:nightly, note that the `latest` tag won't work as it's using the `master` branch which doesn't have plugin support yet, so either use the `nightly` tag or the `develop` tag.

See: https://docs.linuxserver.io/images/docker-lidarr/#version-ta...

Explo is the software used for the discovery https://github.com/LumePart/Explo It automatically downloads daily jams, weekly jams and weekly exploration playlists from your listenbrainz account(free) using youtube, soulseek(with slskd) or lidarr (support was merged very recently).

I also imported all my artists from my spotify account when I migrated which you can do in lidarr with the plugin ̶a̶n̶d̶ ̶t̶h̶e̶ ̶f̶o̶r̶k̶ ̶ bellow ̶b̶e̶c̶a̶u̶s̶e̶ ̶i̶t̶ ̶i̶s̶n̶'̶t̶ ̶s̶u̶p̶p̶o̶r̶t̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶m̶a̶i̶n̶ ̶l̶i̶d̶a̶r̶r̶.̶

plugin: https://github.com/TypNull/Tubifarry

̶f̶o̶r̶k̶ ̶d̶o̶c̶k̶e̶r̶ ̶i̶m̶a̶g̶e̶:̶ ̶g̶h̶c̶r̶.̶i̶o̶/̶l̶i̶n̶u̶x̶s̶e̶r̶v̶e̶r̶-̶l̶a̶b̶s̶/̶p̶r̶a̶r̶r̶:̶l̶i̶d̶a̶r̶r̶-̶p̶l̶u̶g̶i̶n̶s̶

docker image: lscr.io/linuxserver/lidarr:nightly

This plugin is also needed for downloading songs with slsk in lidarr.

https://github.com/rktjmp/playtime.nvim

https://github.com/rktjmp/shenzhen-solitaire.nvim

The author does some cool stuff.

I guess I am lucky as I have watchtower automatically update all my containers to the latest image every morning if there are new versions.

I also just added it to my homelab this sunday, I guess that's good timing haha.

But a life saver is using it with <https://github.com/skeeto/passphrase2pgp>.

This means we don't need to move gpg/ssh keys we can just recreate them by remembering their passphrase (and other stuff like the date if we want).

  # gpg key for the encryption of the password-store
  passphrase2pgp --subkey --protect=2 --uid "helloworld" | gpg --import

  #for access to the git remote repo add to it this public key :
  passphrase2pgp -u emergency -f ssh -p > ~/.ssh/emergency.pub
  #only use it to install a non-emergency key as a new authorized key :
  passphrase2pgp -u emergency -f ssh | ssh-add -

Funnily enough I never used `pass generate` once, even tough I have more than 3700 passwords. I always used the `pwgen` command, I don't know if there really is a big difference between the 2 (except pass generate being already in pass).

As for how to structure, here are some example of how I do it :

  <service>/email
  <service>/otp
  work/<service>/password
  homelab/<service>/username

Then it's very easy to get the password or the otp, just bind `passmenu`, `passmenu-otp` in your window manager or directly use the command line for multiline stuff.