isn’t the algorithm part of the code? or is that split off into a separate repo?

hmmm tips, not sure. You have beets already, that’s the main tip :)

I have it reformatting filenames, storing it in the proper paths, retrieve albumart, and that’s about it I reckon. In case I forgot anyting, I’ll update this message when home.

As for unrecognized albums… That’s tough, I have a bunch of them too. I weighed storing them in the regular folders versus in a separate unrecognized/ folder. Went with the latter approach. I rescan that folder every month, sometimes new matches appear. That unrecognized folder is also shared to navidrome, so except for some missing album art and perhaps improper file/song names, not really an issue.

CI/CD works fine for selfhosted forgejo, I set mine up with minimal hassle.

Thanks for the explanation, something I need to look into!

One benefit of Caddy over NPM: local certificates.

The latest selfh.st newsletter linked to a relevant video:

https://www.youtube.com/watch?v=EVnwnFY7C1w&ref=selfh.st

MusicSeerr

Music Requests

Name: MusicSeerr --> DroppedNeedle

Nice, works with slskd, just what I needed!

argh

^C
$ docker compose up -d

it has become a tic for me xD

Love tempus, it’s my main navidrome client on mobile. Thanks for all the great work!

As much trouble as any regular docker setup I reckon. It’s not doing anything special, just a nice front-end showing the logs, the compose and some details about the different services.

And many of my compose files in there make use of nginx, but the services nginx reference are all inside the same compose.

Perhaps DockGE would help with your flow, it’s a docker web UI for managing services (in a basic manner, think a basic Portainer). It creates the separate folders for you, all you need to do is give the stack a name and plop the compose file in there. I use it to manage containers on all my VMs, mainly to have an easy overview in the browser but also to avoid issues like yours.