I ran Navidrome for a long time, but never found a phone client that held up for my family in the background and in the car. So I wrote a server and its apps together, and it has replaced Spotify for us.

  • one Docker container (Go + SQLite); it reads your music folders and never rewrites your files or tags
  • an account per family member: their own favorites, playlists and personal radio
  • synced lyrics; anyone can nudge lyrics that run early or late
  • native Android (Kotlin) and iPhone apps: background play, lock-screen and car controls, gapless, an offline cache of favorites, and it starts playing when the phone connects to the car
  • optional: add songs from YouTube (yt-dlp) into your own library

The catch: it has its own API, so it is not Subsonic-compatible and your existing clients won’t work with it. It’s about a month old; we use it every day at home.

AI disclosure: built with a lot of help from Claude Code. It wrote most of the code, tests and docs; I designed it, steer it, review what goes in and test it on our phones every day.

Site with a one-minute tour: https://melarka.zexa.se/

  • FridaVermercury@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    ·
    5 days ago

    Sorry you are getting downvoted for the open AI disclosure, at least that is what I assume is happening. I’d also be careful to selfhost and expose anything vibe-coded from someone else on my own machine, but I think its cool you managed to get this all together and its working for you and your family! Just don’t expect others to trust it much.

    One note though, I see it is advertising download from Youtube, this might cause you some problems if you want to continue putting this on github and someone notices. Lots of youtube/youtube music appear and disappear quickly from github these days.

    • aaronsuns@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      4 hours ago

      Thanks, that’s kind, and fair on trust: don’t run it exposed on a stranger’s word. It’s all in the repo to read, and I run it at home behind a VPN. On the YouTube part: the downloader is optional, the server works with just your own music folders, and nothing music-related ships in the repo (the page https://melarka.zexa.se/youtube-to-self-hosted-music says what it does and where the responsibility lies). You’re right that it’s a risk for the repo if YouTube tooling draws takedowns, and I’ll keep that in mind.