Update Vagrantfile

Now runs Panoptes in docker, mounting the local source tree into the
latest image.
To do that would mean going back to having a lengthly build process when provisioning the vagrant box. Do you need to run it with a different ruby that often?

On 9 Oct 2014, at 13:47, Campbell Allen <notifications@github.com> wrote:

> In README.md:
> 
> >  
> > -The Rails application running in the VM will be available at `http://localhost:3000`.
> > -
> > -You can specify either MRI-Ruby or JRuby for the vagrant box by setting $VAGRANT_RUBY to 'mri' or 'jruby' in your shell then running `vagrant provision` (or `vagrant up` if you haven't created the VM yet). By default it will install JRuby.
> > +The Rails application running in the VM will be available at
> > +`http://localhost:3000`. Note that it will take a few minutes for Panoptes to
> > +start. Monitor it with `docker logs panoptes`.
> did we lose the ability to use MRI vs jruby vs env vars? I think we should still be able to switch this.
> 
> —
> Reply to this email directly or view it on GitHub.
>