I’ve tried a few options over the years, including SMB and NFS, XBMC as well as HTML with javascript I found online.
I don’t have a large collection of music (fewer than 100 albums), so hand coding things was actually one of the quicker options to setup. That’s despite then hassle of hand coding the URL to each FLAC file as well as the album art. But sometimes the javascript doesn’t handle large collections of FLAC and each implementation I tried had different quirks so I’ve sunk a lot of time into that in other ways without a satisfactory result.
I’ve heard of Emby, Jellyfin, Plex, Roon and Servio. I just need something that’s simple to set up and access. I don’t need fancy features beyond the ability to play the music with a pleasant UI that can be accessed from the web (HTTP, not HTTPS). I’d be running this from a Raspberry Pi 3B which already has the lighttpd server running.
I’m also considering just getting a portable, 128GB FLAC player with a minijack connection and moving on with my life without getting involved in networking at all.
Any recommendations for an uncomplicated way to approach to doing this?
Edit: Thanks so much for the helpful and enthusiastic comments! I tried Navidrome and had it up and running in ten minutes thanks to this tutorial video: https://invidious.nerdvpn.de/watch?v=7V5UUJlSknY
I had to install docker-compose on the RPi. Then I got an error which turned out to be because I also needed a separate docker daemon which I installed following these instructions: https://www.simplilearn.com/tutorials/docker-tutorial/raspberry-pi-docker
In just 10+ minutes I had my music collection accessible from all my devices - thanks again!
I saw in your update you mentioned installing docker-compose. Modern docker has “compose” as a verb, and should work as
docker compose. I haven’t tested this on raspberry pi though.You’re right. It’s just that the package to installed is called docker-compose (if I remember right. I’m on mobile now). So the command to install was: apt install docker-compose, and the command was: docker compose. Thanks man.
No, thats not how it works now. You used to have to install docker-compose and run
docker-compose, but now you don’t. Docker comes with compose, but you call it asdocker composerather than the old Python module based waydocker-composehttps://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/
Thanks for clarifying. I might be sent to uninstall that other package in that case. It’s all working nicely anyway. Appreciate it, thanks again for your help!