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.

  • minnix@lemux.minnix.devEnglish
    2·
    4 months ago

    I have it installed for a few years now. I started with the AIO but moved to the separate container install after AIO was deprecated. I imagine the install process is too complex for portainer. https://docs.funkwhale.audio/stable/administrator/installation/docker.html

    I did steps 1-4 and skipped the rest because I already have a proxy server running. Don’t remember anything related to snapd though. Mine is running in a Debian 11 VM on proxmox instead of an LXC, but the process should be the same. Also they have a matrix channel for help https://matrix.to/#/#funkwhale-support:matrix.org

    From what I remember it was relatively painless to install, but upgrading can be a chore, especially this last upgrade. My main interest in FW was the federation aspect as far as finding new music. If you don’t care about federation, maybe a simpler option would work better for you.

    • Willdrick@lemmy.worldOPEnglish
      1·
      4 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.devEnglish
        1·
        4 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?