I use Vagrant as a common means of describing a VM. A VBox user on Mac or Linux can launch my box using a known, reputable base image.
The same code and constructs can be used in Vagrant as with other elements or phases of deployment; scripts, runbooks, playbooks, recipies - all can be used locally the same way they might be at cloud scale.
It's a major win for me, I hope Vagrant has a long and fruitful life.
The same code and constructs can be used in Vagrant as with other elements or phases of deployment; scripts, runbooks, playbooks, recipies - all can be used locally the same way they might be at cloud scale.
It's a major win for me, I hope Vagrant has a long and fruitful life.