I ditched Spotify and set up my own music stack

Only components I would swap out here is Cloudflare Tunnels and use of docker.

I have my own tailnet with a self hosted head coordinator (headscale). No need to expose music server to public internet or tie your setup to a service that can easily go down or suddenly find yourself paying for it. Access service from within tailnet

While docker is great for development purposes. I have found for self hosting it adds a bit of overhead (particularly memory and cpu) and complexity to installations (port forwarding between container and host, firewalling, ip discovery, cpu/gpu passthrough). Sure containerization is great if you have the funds/hardware/time and need to scale across thousands of instances/servers. But becomes overkill for these types of use cases.

I would replace with deploying on top of nixOS and manage remotely with nixos-anywhere with declarative configuration.

Going to bookmark this since I have been putting off setting up my own media server. OP tailors to music but also want to make my collection of Blu-ray, and photos accessible.

Docker with Portainer is really simple and much more straightforward to use than having to remember what services run on what ports, etc. I have been self hosting a bunch of apps and web services on an Asustor for a couple of years now, with Cloudflare CDN in front of it, and everything runs smoothly and never breaks.

I just went to the Portainer websites and I can't figure out what it does, exactly. All I know is they've chosen nice fonts. Do you mind explaining what it does for you?

It adds a GUI to Docker so that you can manage your containers from a web page instead of the cli (create, configure, start/stop, etc.) You don't need it if you know Docker well but it's a nice to have.