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
53 lines
2.7 KiB
Markdown
53 lines
2.7 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Why Vagrant?"
|
|
sidebar_current: "why"
|
|
description: |-
|
|
Vagrant provides easy to configure, reproducible, and portable work
|
|
environments built on top of industry-standard technology and controlled by a
|
|
single consistent workflow to help maximize the productivity and flexibility
|
|
of you and your team.
|
|
---
|
|
|
|
# Why Vagrant?
|
|
|
|
Vagrant provides easy to configure, reproducible, and portable work environments
|
|
built on top of industry-standard technology and
|
|
controlled by a single consistent workflow to help maximize the productivity
|
|
and flexibility of you and your team.
|
|
|
|
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 be used to automatically install
|
|
and configure software on the machine.
|
|
|
|
## How Vagrant Benefits You
|
|
|
|
If you are a **developer**, Vagrant will isolate dependencies and their
|
|
configuration within a single disposable, consistent environment, without
|
|
sacrificing any of the tools you are used to working with (editors, browsers,
|
|
debuggers, etc.). Once you or someone else creates a single [Vagrantfile](/docs/vagrantfile/), you just need to `vagrant up` and everything is installed and
|
|
configured for you to work. Other members of your team create their
|
|
development environments from the same configuration, so whether you are working
|
|
on Linux, Mac OS X, or Windows, all your team members are running code in
|
|
the same environment, against the same dependencies, all configured the same way.
|
|
Say goodbye to "works on my machine" bugs.
|
|
|
|
If you are an **operations engineer**, Vagrant gives you a disposable environment
|
|
and consistent workflow for developing and testing infrastructure management
|
|
scripts. You can quickly test things like shell scripts, Chef cookbooks,
|
|
Puppet modules, and more using local virtualization such as VirtualBox or
|
|
VMware. Then, with the _same configuration_, you can test these scripts
|
|
on remote clouds such as AWS or RackSpace with the _same workflow_. Ditch
|
|
your custom scripts to recycle EC2 instances, stop juggling SSH prompts
|
|
to various machines, and start using Vagrant to bring sanity to your life.
|
|
|
|
If you are a **designer**, Vagrant will automatically set everything up that is required
|
|
for that web app in order for you to focus on doing what you do best:
|
|
design. Once a developer configures Vagrant, you do not need to worry about
|
|
how to get that app running ever again. No more bothering other developers
|
|
to help you fix your environment so you can test designs. Just check out the
|
|
code, `vagrant up`, and start designing.
|