Deebster

I think so - I'm in Asia atm and nothing from feddit loads

I think I need to spend a while watching and reading everything this guy's ever done, especially if it's in this dry, understated humour.

The old footage looked like Robot Wars if they didn't have any safety requirements.

After being virtually dead, it's had a lot more development over the last few years(?), with steady progress towards passing the tests and supporting the specs (including reporting spec bugs and vagueness). It's still a long way from being generally usable.

The focus is on making something that could be embeddable, although there are basic browsers using that embed. The focus seems to be on for use-cases like Electron, which doesn't need all of the web APIs.

I don't use it or contribute (yet), but I have their blog in my RSS reader and so keep an eye on it.

What names has this process come up with?

I like that one of the first things I see is The UX of LEGO Interface Panels - you've got yourself another subscriber!

Thanks, added to my to-read list.

I can't help much there, I've only favourited albums and they were handled by the upgrade script.

I assume the change is due to the persistent id feature, but I don't know why the upgrade script couldn't handle it (although I'm assuming it's too error prone to do automatically because of duplicate artist names).

My guess would be you should open your pre-upgrade database and export a list, and then use that to add them again to the post-upgrade database. If you'd tagged your files with musicbrainz (Picard) then you should be able to find the PIDs without too much trouble.

Alternatively, you could change your settings to use the old matching "legacy" style if you don't have tags that are useful for PID.

Hmm, good point - I guess he didn't want to go to version 1.0 yet (I have no idea if 1.0 is on the roadmap or if it's another project that will forever stay as 0.x)

The writing of Julie Czerneda is very creative when it comes to alien species.

I haven't read anything by her, where do you recommend I start?

I've talked about my setup a little recently.

Here's my quadlet file for Navidrome:

[Unit]
Description=Navidrome music server
After=mnt-files.mount

[Container]
ContainerName=navidrome
Image=docker.io/deluan/navidrome:latest
AutoUpdate=registry
User=1116:1116
UserNS=nomap
Network=navidrome.network
PublishPort=4533:4533
Environment=ND_LOGLEVEL=info
Environment=ND_SCANNER_SCHEDULE=1h
Environment=ND_BACKUP_PATH=/backup
Environment=ND_BACKUP_SCHEDULE=@midnight
Environment=ND_BACKUP_COUNT=7
Environment=ND_SESSIONTIMEOUT=72h
Environment=ND_BASEURL=""
Environment=ND_COVERARTPRIORITY="coverart.*, cover.*, folder.*, front.*, embedded, external"
Environment=ND_SPOTIFY_ID=aaaa
Environment=ND_SPOTIFY_SECRET=bbbb
Environment=ND_LASTFM_APIKEY=cccc
Environment=ND_LASTFM_SECRET=dddd
Volume=${HOME}/navidrome/data:/data:Z,U
Volume=${HOME}/navidrome/backup:/backup:Z,U
Volume=/mnt/files/music:/music:ro
HealthCmd=wget -q -t1 --spider --proxy off localhost:4533 || exit 1

[Service]
Restart=always

[Install]
WantedBy=default.target

There's bit going on here, as I've got lots of optional stuff set up.

I don't use a config file if I don't want to/can't do config reloading, which is why there's loads of env vars - it's just easier to have everything in one file.

Podman is running rootless, and Navidrome is running as UID 1116 within the container (and as 656476 on the host system as it's a subuid of the podman user). Same for GID.

The Z,U bit on the volumes might need explaining - Z means apply a private SELinux label, U means set the volume's UID+GID on the host to match inside the container (after mapping to user namespaces, that is).

I have this in podman with autoupdate, so I'm already running the new version - logs says startup took 833 seconds, so be patient when it upgrades.

I had to rename the ND_SCANSCHEDULE env var to ND_SCANNER_SCHEDULE (and restart again) but that was the only hitch for me.

Not really a "not the onion" story.