Vagrant is used to quickly spin up, provision, and destroy (and rinse-repeat) VMs for development, testing, etc. You can install Vagrant on a physical server and spin up Vagrant VMs (which is probably what most ppl do) and provision servers as needed to your specifications. If you had a virtualized environment like VMware, Hyper-V, etc. I'd end up using VM templates and provision using Puppet, Chef, Ansible, Salt, etc. then kill the VMs and re-do as needed.
On Thursday, July 10, 2014 11:38:59 AM UTC-4, Matthew Krieger wrote: > > Is there anything about Vagrant that makes it inappropriate for use in > physical (non-virtual machine) environments? I see that most of the > verbiage in the docs etc about Vagrant is about VMs. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
