Welcome to the exciting world of
GiddyUp is the visual scorecard for riak_test. GiddyUp
provides two services, seeding
riak_test with the list of tests which should be run for
each platform, and receiving tests results and logs via a REST interface.
- Install Postgres. e.g.
brew install postgresql
- Initialize Postgres
initdb /usr/local/var/postgres -E utf8
- Start Postgres:
pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start
- Create your dev database
- Test it out:
psql -h localhost giddyup_dev
Also, install this: get the heroku-toolbelt
- Create a
.envfile with the following environment variables:
- Migrate your database using
foreman run rake db:migrate
- Seed your database with the default set of tests, platforms and
backend combinations using
foreman run rake db:seed
- Start your application with
Want to add a new migration? try
bundle exec rake db:new_migration[MigrationName]!
Fun Fact: zsh hates 's. try adding
setopt nonomatch to your .zshrc to make it love them,
unless you are the yesnomatch type, in which case, run
noglob bundle exec rake db:new_migration[MigrationName]. Don't say I did't warn you.
Your best bet is to get the current heroku dataset with
pg_dump. You need the heroku database
url, which you can get with
heroku config if you have access. If you don't, you shouldn't be
pg_dump -O -x postgres://whatever > heroku.sql dropdb giddyup_dev createdb giddyup_dev psql giddyup_dev < heroku.sql
Once you start giddyup after that, you should have a mirror of production. Try out your migration now. the end.
Each combination of test and platform will either succeede or fail. Success is indicated by a green badge, failure by a red badge.
The text of a badge indicates the data store followed by the relative version. "U" indicates neither was specified. "L" indicates eleveldb, "M" uses memory, and "B" indicates bitcask. After the optional memory specified, the relative version is specified. "-1" indicates previous; "-2" indicates legacy.