If you're interested about the scripts themselves and their behaviour, this post is for you.

Basically, the installation script is responsible for:
1. Asking configuration values (domain name, admin password, etc.) from the user
2. Downloading and installing ansible
3. Install Funkwhale using our ansible role (https://dev.funkwhale.audio/funkwhale/ansible/)
4. Creating an Ansible playbook with the provided configuration
5. Running the playbook

So, the script doesn't actually perform the installation of Funkwhale. Ansible does, which is better, because it's more tested and more trustable.

As for the update script, it's even simpler:

1. Retrieve the latest version
2. Update the version number in the ansible playbook
3. Rerun our playbook with the updated configuration

One thing I was really careful with when writing this script was to give enough feedback to the user.

I like scripts that handle the complexity for me, but I hate when they try to *hide* it from me, because it means I can never understand what's going on and learn.

As a result, those scripts are verbose. They tell you what's going on, what command (especially ansible commands) are run, what is about to happen.

@eliotberriot great great work. Thank you.

@June you're welcome :3

@tykayn thank you for giving it a try, I'm so happy it worked for you 😌

As for your question, you can put the music in /srv/funkwhale/data/music (or set this to a symlink to our actual directory)

Then follow the instructions here: https://docs.funkwhale.audio/admin/importing-music.html#from-music-directory-on-the-server

(note that you need to run /srv/funkwhale/manage instead of python api/manage.py, but the remainder of the commands should be the same)

@eliotberriot awesome, worked very well on a few hundred titles. still i get some mp3 files that i cannot import, because of a TypeError 'NoneType' object is not subscuptable.
i will check that on the Riot channel

@tykayn sure, see you there!