b1f14087e5
The vagrant-aws provider doesn't really make sense anymore to be mentioned in the getting started guide for providers. Instead, replace it with the Hyper-V provider.
1.7 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| intro | Providers - Getting Started | gettingstarted-providers | In this getting started guide, your project was always backed with VirtualBox. But Vagrant can work with a wide variety of backend providers, such as VMware, Hyper-V, and more. Read the page of each provider for more information on how to set them up. |
Providers
In this getting started guide, your project was always backed with VirtualBox. But Vagrant can work with a wide variety of backend providers, such as VMware, Hyper-V, and more. Read the page of each provider for more information on how to set them up.
Once you have a provider installed, you do not need to make any modifications
to your Vagrantfile, just vagrant up with the proper provider and
Vagrant will do the rest:
$ vagrant up --provider=vmware_fusion
Once you run vagrant up with another provider, every other Vagrant
command does not need to be told what provider to use. Vagrant can automatically
figure it out. So when you are ready to SSH or destroy or anything else,
just run the commands like normal, such as vagrant destroy. No extra
flags necessary.
For more information on providers, read the full documentation on providers.
Next Steps
That's it! You have successfully completed the getting started guide for Vagrant. Here are some interesting topics you might find relevant: