beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #12473 from soapy1/docs-fixes

Browse Source 
Grammatical fixes
This commit is contained in:
Sophia Castellarin 2022-07-29 08:59:11 -05:00 committed by GitHub
commit 7e54c83192
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/intro/index.mdx
View File

@ -30,7 +30,7 @@ To achieve its magic, Vagrant stands on the shoulders of giants. Machines
are provisioned on top of VirtualBox, VMware, AWS, or
[any other provider](/docs/providers/). Then, industry-standard
[provisioning tools](/docs/provisioning/)
such as shell scripts, Chef, or Puppet, can automatically install
such as shell scripts, Chef, or Puppet can automatically install
and configure software on the virtual machine.
### For Developers

10
website/content/intro/vs/cli-tools.mdx
View File

@ -2,7 +2,7 @@
layout: intro
page_title: Vagrant vs. CLI Tools
description: |-
Virtualization software like VirtualBox and VMware come with command line
Virtualization software like VirtualBox and VMware comes with command line
utilities for managing the lifecycle of machines on their platform. Vagrant
actually uses many of these utilities internally. The difference between these
CLI tools and Vagrant is that Vagrant provides a declarative, reproducible,
@ -19,19 +19,19 @@ actually uses many of these utilities internally.
The difference between these CLI tools and Vagrant is that Vagrant builds
on top of these utilities in a number of ways while still providing a
consistent workflow. Vagrant supports multiple synced folder types, multiple
provisioners to setup the machine, automatic SSH setup, creating HTTP tunnels
into your development environment, and more. All of these can be configured
provisioners to set up the machine, automatic SSH setup, creating HTTP tunnels
into your development environment and more. All of these can be configured
using a single simple configuration file.
Vagrant still has a number of improvements over manual scripting even if you
ignore all the higher-level features Vagrant provides. The command-line
ignore all the higher-level features Vagrant provides. The command line
utilities provided by virtualization software often change each version
or have subtle bugs with workarounds. Vagrant automatically detects the
version, uses the correct flags, and can work around known issues. So if
you're using one version of VirtualBox and a co-worker is using a different
version, Vagrant will still work consistently.
For highly-specific workflows that don't change often, it can still be
For highly specific workflows that don't change often, it can still be
beneficial to maintain custom scripts. Vagrant is targeted at building
development environments but some advanced users still use the CLI tools
underneath to do other manual things.