From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/vagrant/providers%2Findex.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 devdocs/vagrant/providers%2Findex.html (limited to 'devdocs/vagrant/providers%2Findex.html') diff --git a/devdocs/vagrant/providers%2Findex.html b/devdocs/vagrant/providers%2Findex.html new file mode 100644 index 00000000..1931f338 --- /dev/null +++ b/devdocs/vagrant/providers%2Findex.html @@ -0,0 +1,6 @@ +

Providers

While Vagrant ships out of the box with support for VirtualBox, Hyper-V, and Docker, Vagrant has the ability to manage other types of machines as well. This is done by using other providers with Vagrant.

Alternate providers can offer different features that make more sense in your use case. For example, if you are using Vagrant for any real work, VMware providers are recommended since they're well supported and generally more stable and performant than VirtualBox.

Before you can use another provider, you must install it. Installation of other providers is done via the Vagrant plugin system.

Once the provider is installed, usage is straightforward and simple, as you would expect with Vagrant. Read into the relevant subsections found in the navigation to the left for more information.

+

+ © 2010–2018 Mitchell Hashimoto
Licensed under the MPL 2.0 License.
+ https://www.vagrantup.com/docs/providers/ +

+
-- cgit v1.2.3