update vagrant provisioning

## motivation

Vagrant provisioning was failing intermittently on CI.
Well - so long as we're all on board with dropping our development
databases every time we re-provision, it's fine.


On Thu, Aug 14, 2014 at 5:59 PM, Joshua Moody <notifications@github.com>
wrote:

> In provisioning/base.yml:
>
> > @@ -46,5 +46,5 @@
> >      - name: installing necessary gems
> >        shell: source /etc/profile && cd /vagrant && gem install bundler && rbenv rehash && bundle install executable=/bin/bash
> >      - name: set up databases
> > -      shell: source /etc/profile && cd /vagrant && bundle exec rake db:setup && RAILS_ENV=test bundle exec rake db:drop db:create db:schema:load executable=/bin/bash
> > +      shell: source /etc/profile && cd /vagrant && bundle exec rake db:reset && RAILS_ENV=test bundle exec rake db:drop db:create db:schema:load executable=/bin/bash
>
> Locally and on CI, I was seeing this:
>
> stderr: wetap-api_development already exists
>
> Full stack trace is here:
> https://gist.github.com/jmoody/0b9e36c438b47cb0d074
>
> Did I do wrong?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wetap/wetap-api/pull/25/files#r16272233>.
>