Getting started structure and "Why Vagrant?" page
This commit is contained in:
parent
0f8ad73cbc
commit
2fd4bec6a1
|
@ -1,7 +1,13 @@
|
|||
{% include header.html %}
|
||||
<div class="grid_3 alpha sidebar">
|
||||
<ol>
|
||||
<li><a href="/docs/user-guide/index.html">Introduction to Vagrant</a></li>
|
||||
<li><a href="/docs/getting-started/index.html">Overview</a></li>
|
||||
<li><a href="/docs/getting-started/why.html">Why Vagrant?</a></li>
|
||||
<li><a href="/docs/getting-started/introduction.html">Introduction and Setup</a></li>
|
||||
<li><a href="/docs/getting-started/boxes.html">Boxes</a></li>
|
||||
<li><a href="/docs/getting-started/provisioning.html">Provisioning</a></li>
|
||||
<li><a href="/docs/getting-started/ports.html">Port Forwarding</a></li>
|
||||
<li><a href="/docs/getting-started/packaging.html">Packaging</a></li>
|
||||
</ol>
|
||||
</div>
|
||||
<div class="grid_9 omega guide">
|
||||
|
|
|
@ -4,11 +4,13 @@ title: Getting Started
|
|||
---
|
||||
# Getting Started with Vagrant
|
||||
|
||||
Web developers use virtual environments every day with their web applications. From EC2 and Rackspace Cloud to specialized
|
||||
solutions such as EngineYard and Heroku, virtualization is the tool of choice for easy deployment and infrastructure management.
|
||||
Vagrant aims to take those very same principals and put them to work in the heart of the application lifecycle.
|
||||
By providing easy to configure, lightweight, reproducible, and portable virtual machines targeted at
|
||||
development environments, Vagrant helps maximize your productivity and flexibility.
|
||||
Vagrant uses [Sun's VirtualBox](http://www.virtualbox.org)
|
||||
to build configurable, lightweight, and portable virtual machines dynamically.
|
||||
The first couple pages serve to introduce you to Vagrant and what it has
|
||||
to offer while the rest of the guide is a technical walkthrough for building a
|
||||
fully functional Ruby on Rails development environment. The getting started
|
||||
guide concludes by explaining how to package the newly created vagrant environment
|
||||
so other developers can get up and running in just a couple commands.
|
||||
|
||||
## Install Vagrant
|
||||
|
||||
|
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
layout: getting_started
|
||||
title: Getting Started - Why Vagrant?
|
||||
---
|
||||
# Why Vagrant?
|
||||
|
||||
Web developers use virtual environments every day with their web applications. From EC2 and Rackspace Cloud to specialized
|
||||
solutions such as EngineYard and Heroku, virtualization is the tool of choice for easy deployment and infrastructure management.
|
||||
Vagrant aims to take those very same principals and put them to work in the heart of the application lifecycle.
|
||||
By providing easy to configure, lightweight, reproducible, and portable virtual machines targeted at
|
||||
development environments, Vagrant helps maximize your productivity and flexibility.
|
||||
|
||||
Vagrant is a development tool which stands on the shoulders of giants, using tried and
|
||||
proven technologies to achieve its magic. Vagrant uses [Sun's VirtualBox](http://www.virtualbox.org)
|
||||
to create its virtual machines and then uses [Chef](http://www.opscode.org/chef) to provision them.
|
||||
|
||||
## Benefits of Vagrant
|
||||
|
||||
### For Solo Developers
|
||||
|
||||
### For Teams
|
||||
|
||||
### For Companies
|
Loading…
Reference in New Issue