* Use docker-compose to run database setup
* Build sidekiq image in test script
* Fix db migration startup script
* Let Runit deal with services
Sidekiq was started by a blocking script in my_init. This lead to the init process not getting to run Runit, which is in charge of CRON among other things. To fix it, I moved Sidekiq to be run by Runit as well. I also moved the postfix start script, while I was at it.
* Fix sidekiq init script
* Re-evaluate `git clone` if snpr's master changed
* Pass along SNPR_REV env var to docker
* Find out snpr commit hash if not passed in
* Only build "rails" image explicitly
* Make the sidekiq init script work
* Fix migrate init script
* Simplify Dockerfile
* Sudo is required if you do it correctly
* Build sidekiq image with docker-compose
* Push sidekiq image to docker hub
* Only push to Docker Hub if build is not a pull-request
* Reduce number of places where Ruby versions are specified
* Add TravisCI config
* Let's see which Ruby the app user uses
* Set Ruby version as app user
* Use full path for calling rvm
* Same but different
* Use rvm Ruby throughout
* Try setting up Postgres on TravisCI
* Remove passenger_ruby nginx directive
It should be the default... maybe...
* fixup! Try setting up Postgres on TravisCI
* Use Docker Compose
* Don't wait 10 seconds
* Try multiple times before drawing conclusions
* Explicitly set a password for postgres
* Try pruning volumes
* Also retry db setup if request failed
* Do we actually need to build before up?
* Move empty lines around
* Turns out, no sudo needed
