Does not perform database upgrade on update from 2.x to 2.1

[ViViDboarder]

I had to do this manually. It seems like something that Ansible could do since it runs the playbook every time the container starts.

[ViViDboarder]

I suppose this could also be handled by the web application as well.

[xsteadfastx]

i agree that it would be the best to do in the web application. right now i didnt found a way to check the current version and the db version to run the command if its needed.

[j0k3r]

Migrate command has been added in #48

[ViViDboarder]

Great patch. That's certainly useful for what I was suggesting here, but I was wondering why one would need to run the migrate command themselves at all. Couldn't the Ansible playbook check the database version and run migrate on a standard run? This resolved situations where users are unsure when an update requires a migration.

…

On Wed, Feb 1, 2017, 2:09 AM Jeremy Benoist ***@***.***> wrote: Closed #34 <#34>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIXQca8s2XZRJ5P8t5j0lLulLpVFPfIks5rYFnXgaJpZM4K6El_> .

[xsteadfastx]

i think its pretty dangerous to run the migrations all the time. i didnt found a way how to find out what version the db is... maybe someone has an idea.

…

On Wed, 01. Feb 07:25, Ian wrote: Great patch. That's certainly useful for what I was suggesting here, but I was wondering why one would need to run the migrate command themselves at all. Couldn't the Ansible playbook check the database version and run migrate on a standard run? This resolved situations where users are unsure when an update requires a migration.