I get music from a variety of sources. Mostly torrents or soulseek. Both are hooked up through Lidarr but I also like to use the soulseek daemon web UI. I also buy off Bandcamp and download from the browser. Less often I get files from friends. All sources lead to “inbox” folders for Beets-flask, which handles tagging and then importing to the actual library. Navidrome serves the library up for clients. Koito handles scrobbles.

I’ve been trying out Aurral for recommendations and playlist generation but I’m not loving it. Pretty quick I learned it wants me to stream from it’s subsonic API (in place of Navidrome) for best results. I can’t figure out if it will work just off my Koito scrobble history.

Will try Audiomuse AI at some point. Auto playlist generation would make my stack feel more “modern” I think.

I like the flexibility that proxmox provides me. I do this as a hobby and I’m self taught. I can try a bunch of things and if I mess up I can start over without much hassle.

I use rclone, not restic, to back up to backblaze. So maybe my advice is not relevant to restic. But what I’m going to say isn’t touched on in other comments, so I’ll put it out there.

The rclone docs say for Backblaze in particular, users should increase the number of concurrent file transfers because rclone’s default (4 concurrent transfers) is too slow on Backblaze. I don’t see this mentioned in other rclone docs pages for other providers (of the ones I’ve looked at: Jottacloud, Overdrive, I forget what else). My impression is it’s something about Backblaze. Maybe its something you could look into.