Add possibility to handle remote managed postgresql setup

This is to address another part of issue #6 (closed)

This has been only partly tested (on the new possibility of remote postgresql setup), on classic (remote) Ansible deployment, but not through the shell script + ansible mix installation.

The new keys have been set in order to match current expectations (i.e. a local install of postgresql).

I end up declaring funkwhale_database_url in playbook and modifying DATABASE_URL in .env (it feels redundant).

marked as a Work In Progress

changed the description

added 1 commit

• e4d3ba5d - change in .env

Compare with previous version

changed the description

unmarked as a Work In Progress

@popindavibe thank you for working on this. The tests seem to pass, so you likely didn't break the install script ;)

Once we've sorted out my comments, do you mind adding a few lines to the table in README.rst to document the new variables? I can do it otherwise.

added 1 commit

• eca488f6 - change in .env

Compare with previous version

Pushing new modifications:

• separate tasks whether or not postgresql is local
• commenting out funkwhale_database_url in default/main.yml since it will only be necessary to set it up when you have funkwhale_database_managed: false
• adding if for password in .env

First point raised is still pending further info.

oops, I broke the install script...

added 1 commit

• 0ce0eebd - change in .env

Compare with previous version

added 1 commit

• 7bfbe025 - change in .env

Compare with previous version

• removing the funwhale_database_host_app bit in .env if it's localhost