Has anybody here managed to install Funkwhale using Portainer? I’ve already tried 3 times, first tried a template, but turns out the AIO container is deprecated, then tried modifying the default docker-compose and env files available on Funkwhale’s repo, didn’t work (couldn’t run the required commands to create a user). Then I spun up a brand new debian 12 LXC container on proxmox, ran their quick install script and failed (something related to snapd, even though it was installed).

Up until now I’ve been an avid Navidrome user, but since we’ve been cutting some costs, Spotify had to go. Too late I realised Navidrome has no library separation: Even though you can have multiple users, they all pull from the same library, making it a mess.

I’m just looking for a simple deployment I can use either within my LAN or via TailScale, just for me and a few family members.

  • Willdrick@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    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.

    • minnix@lemux.minnix.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      I guess I don’t understand. You followed the docker installation directions correctly and it didn’t work or you modified the directions in a way that you prefer and it didn’t work?