On initial load of localhost:4000, the http calls for
additional Javascript files via the browser appears to take
more than a few minutes with *.js endpoints loading in one
file at a time very slowly.
It was observed that the Ruby process was consistently
pegged at 95% and up. This behaviour is not observed
using a Mac OSX.
However, adding a single core to the guest OS
(from 1 to 2) improved performance considerably.
The patch detects if the host system is Mac OSX or
Linux and attempts to assign the same number of cores
as is present on the host.
added the "trim_trailing_white_space_on_save setting" so developpers
using sublime text will now trim trailing white space one save
updated the vagrant configuration file so it uses ruby convention
This introduces two configuration management runs into the
Vagrant provisioning phase. The first chef-solo run ensures that
a current version of chef is installed using the omnibus updater.
The second chef-solo run installs vim and phantomjs.
Much more is possible, this is a proof of concept.
Cookbooks are stored in the chef directory, and managed by
librarian-chef, which is like a bundler for cookbooks.
Chef is run when VM is first downloaded and booted, but not on
subsequent halt/up cycles. To force chef to run again, use
`vagrant provision`.
Increase memory allocation to 512MB so guest VM is not swapping.
SSH forwarding, DNS host nat resolver.
Don't use NFS on darwin, just use standard folder sharing.
