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. 
Fair enough. Might I suggest changing it slightly to:

    if docker inspect panoptes_console >/dev/null 2>/dev/null; then

To just test the return value directly, and also to suppress the output so it doesn’t flood the terminal. Also note there’s no need to run docker in sudo since the vagrant user is in the docker group.

On 15 Oct 2014, at 13:05, Edward Paget <notifications@github.com> wrote:

> In vagrant_scripts/console.sh:
> 
> > @@ -0,0 +1,14 @@
> > +#! /bin/bash
> > +
> > +sudo docker inspect panoptes_console
> > +
> > +if [ $? = 1 ]; then
> I don't want to remove the container each time so we don't have to re bundle on every run.
> 
> I can't imagine they would change docker inspect to return 0 when it can't find a named container either. Its also a pretty simple change if they do for some reason.
> 
> —
> Reply to this email directly or view it on GitHub.
>