the problem with FW’s docs is that they are too opinionated, they expect a strict user and directory structure that should not be required for docker deployments. I modified the example docker-compose to use volumes instead of binding to host locations (except for the music:ro folder) and it didn’t like it at all. I get that they prefer using ansible playbooks over docker, but even when starting from a fresh debian 12 install it’d fail, even though I followed that guide to the tee.
As someone else said on the thread, it’s weird but there’s no much choice for multi-library music-centric servers. Guess I’ll have to wrangle Jellyfin into submission to tag my music properly.
Nice, I might give that a go. So instead of doing Artist/Album/songfile.ext you just have all albums in the same level? e.g. Band - Album1/song1.mp3 Band - Album2/song1.flac
If that’s so, I might be able to batch sort them to that structure and give Jellyfin another try