It doesn't. This was a rudimentary first pass. My plan is to package a
preconfigured box exclusively for jQuery dev. Will need far less ram.
On Oct 28, 2013 9:40 AM, "Carl Danley" <notifications@github.com> wrote:

> In Vagrantfile:
>
> > @@ -0,0 +1,88 @@
> > +# -*- mode: ruby -*-
> > +# vi: set ft=ruby :
> > +
> > +dir = Dir.pwd
> > +vagrant_dir = File.expand_path( File.dirname( __FILE__ ) )
> > +
> > +Vagrant.configure( "2" ) do |config|
> > +
> > +  # Store the current version of Vagrant for use in conditionals when dealing
> > +  # with possible backward-compatibility issues.
> > +  vagrant_version = Vagrant::VERSION.sub( /^v/, '' )
> > +
> > +  # Configurations from 1.0.x can be placed in Vagrant 1.1.x specs like the following.
> > +  config.vm.provider :virtualbox do |v|
> > +    v.customize ["modifyvm", :id, "--memory", 512]
>
> Not too sure it *needs* to be 512MB; might be able to bump this down to
> 256MB. Thoughts? It ran rather fine when we had it set to 256MB in our
> original versions of https://github.com/10up/varying-vagrant-vagrants but
> we bumped it up later due to the extra stuff running.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jquery/jquery/pull/1410/files#r7247668>
> .
>