rake:setup shouldn't truncate/drop the database
Created by: gdamjan
I'm writing a deployment playbook for gitlab in ansible.
The problem is that if I run bundle exec rake gitlab:setup RAILS_ENV=production after gitlab has been used it'll clear the database, which means if I run the playbook a second time it'll flush my database.
I would be ideal if there was a gitlab:setup_or_update rake task that would do the right thing whenever it's a new install or an update.