haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Replace AWS provider in getting started guide with Hyper-V 

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.
This commit is contained in:
Brian Cain 2019-05-13 14:25:00 -07:00
parent e91a1aadc4
commit b1f14087e5
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/intro/getting-started/providers.html.md
View File

@ -5,7 +5,7 @@ sidebar_current: "gettingstarted-providers"
description: |-
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,
AWS, and more. Read the page of each provider for more information on how to
Hyper-V, and more. Read the page of each provider for more information on how to
set them up.
---
@ -14,7 +14,7 @@ description: |-
In this getting started guide, your project was always backed with
[VirtualBox](https://www.virtualbox.org). But Vagrant can work with
a wide variety of backend providers, such as [VMware](/docs/vmware/),
[AWS](https://github.com/mitchellh/vagrant-aws), and more. Read the page
[Hyper-V](/docs/hyperv), 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
@ -25,12 +25,6 @@ Vagrant will do the rest:
$ vagrant up --provider=vmware_fusion
```
Ready to move that to the cloud? Take it to AWS:
```
$ vagrant up --provider=aws
```
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,