[ericclemmons]

The most important part of using vagrant, the provisioning, isn't even covered in the article.

A paragraph or link to vagrant's homepage is enough to explain the value. The hardest part is automating the dev environment via chef or puppet, which is where the article should've been dedicated to.

[dljsjr]

There is a link to the Vagrant docs on running chef solo at the bottom of the article. Not sure if it was always there or if it was a response to this comment because the author made no indication of edit or update.

[ericclemmons]

That comment was there in the original.

My point was that the provisioning (or packaging of a VM) is the most crucial and discussion-worthy aspect of setting up Vagrant. At least in my experience, that's the hurdle for people to overcome when seeing the value of Vagrant, as they usually already have VMWare or VirtualBox VMs running.

[wootticus]

There's a few ways to get by without Chef or Puppet. Once your dev environment is set up you can run "vagrant package" and redistribute the vm with your modifications.

You could also use shell provisioner instead.