5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
1.3 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| docs | Default Provider - Providers | providers-default | By default, VirtualBox is the default provider for Vagrant. VirtualBox is still the most accessible platform to use Vagrant: it is free, cross-platform, and has been supported by Vagrant for years. With VirtualBox as the default provider, it provides the lowest friction for new users to get started with Vagrant. |
Default Provider
By default, VirtualBox is the default provider for Vagrant. VirtualBox is still the most accessible platform to use Vagrant: it is free, cross-platform, and has been supported by Vagrant for years. With VirtualBox as the default provider, it provides the lowest friction for new users to get started with Vagrant.
However, you may find after using Vagrant for some time that you prefer
to use another provider as your default. In fact, this is quite common.
To make this experience better, Vagrant allows specifying the default
provider to use by setting the VAGRANT_DEFAULT_PROVIDER environmental
variable.
Just set VAGRANT_DEFAULT_PROVIDER to the provider you wish to be the
default. For example, if you use Vagrant with VMware Fusion, you can set
the environmental variable to vmware_fusion and it will be your default.