Vendored go.rice manually as a submodule. This is so that Godep picks up its
dependencies as well, so that the entirety of Drone's dependencies are
vendored in, and Drone can be built without an internet connection.
At least until https://github.com/plouc/go-gitlab-client/pull/8
accepted or Drone officially fork it to `drone/go-gitlab` or
when we have package management which can do something like this:
gom 'github.com/plouc/go-gitlab-client',
:github => 'fudanchii/go-gitlab-client', :branch => 'raw-request'
This includes refactoring database setup, and migration system.
Remove setupDatabase from main and use `Init` method from database
package.
At database package, defines Init method which actually initiate
database with options given from comand line flag. I think `--path`
wont be used anywhere so I plan to remove it later.
Both meddler and migration initiated here, then we call `Set` method
to setup all the tables, etc. Here I think I want to separate database
schema and turn it into migration script instead, later maybe.
At migration package I made some tweak to `Operation` interface.
Realized that it's ludicrous to let migration driver re-implement `Exec`
and `Query`, I made migration script to receive The whole
migrationDriver struct which contains both Operation implementor, and
the Tx itself. This made possible thanks to Go struct being able to
promote its member, now our migration is more transparent.
There's also stub implementation for bot mysql and postgresql, will
implement this really soon.
