So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own?
Perhaps there should be a "Production/deployment" section of the Getting Started Guide.
I've set up scripts to convert an existing virtualbox/vagrant .box file to a vmware compatible OVF. I would use those to deliver to clients at my last employer. I know github is doing a similar process. Additionally there's mccloud, which lets you deploy to aws. If you need help getting any of these set up, let me know.
Thanks for the feedback. I agree there should probably be a section on this in the documentation since it is a common question.
But you're on the right track: The puppet/chef provisioning you use in the VM should be used for production as well. Usually the scripts aren't IDENTICAL in dev/production but there are only slightly different.
So, Vagrant lets you setup quick VMs to make development easier. I get that... (and like it). But what happens when you need to migrate the dev image to actual hardware? I assume that you use the same Puppet / Chef provisioning that you use in the VM, but it isn't clear from the "Getting Started" part of the site. Does Vagrant help with that, or are you on your own?
Perhaps there should be a "Production/deployment" section of the Getting Started Guide.