Update vagrant

Closes #199 

This adds a couple scripts to launch a rails console and run the spec suite. They can serve as guides for how to run other rails services from inside docker. 
I think that’s actually the intention here. If it’s been created already then the script starts it, otherwise it creates it. I’m not sure that just checking the return code from `docker inspect` is future-proof though, so it might be better to test whether the container exists more directly (e.g. by parsing the output from `docker inspect` with jshon or something).

On 15 Oct 2014, at 11:55, Campbell Allen <notifications@github.com> wrote:

> In vagrant_scripts/console.sh:
> 
> > @@ -0,0 +1,14 @@
> > +#! /bin/bash
> > +
> > +sudo docker inspect panoptes_console
> > +
> > +if [ $? = 1 ]; then
> Seems the docker inspect comand will return data for created but not running containers and thus the exit code for this will be 0.
> 
> Probably best just to test with ps from the vagrant os to detect if the rails c is running. @astopy thoughts?
> 
> —
> Reply to this email directly or view it on GitHub.
>