Getting started on the pages
This commit is contained in:
Mitchell Hashimoto
parent
f6a617c643
commit
87d6a85c4b
|
|
@ -3,15 +3,15 @@
|
|||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en-us">
|
||||
<head>
|
||||
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
|
||||
<title>Vagrant</title>
|
||||
<title>Vagrant - {{ page.title }}</title>
|
||||
|
||||
<meta name="description" content="Create and manage virtualized development environments." />
|
||||
|
||||
<link rel="stylesheet" href="css/reset.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="css/text.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="css/960.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="css/screen.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="css/syntax.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="/css/reset.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="/css/text.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="/css/960.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="/css/screen.css" type="text/css" media="screen" />
|
||||
<link rel="stylesheet" href="/css/syntax.css" type="text/css" media="screen" />
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
<div id="navigation">
|
||||
<ul id="nav">
|
||||
<li><a href="/">home</a></li>
|
||||
<li><a href="/about.html">about</a></li>
|
||||
<li><a href="/docs/getting_started.html">get started</a></li>
|
||||
<li><a href="/documentation.html">documentation</a></li>
|
||||
<li><a href="/contribute.html">contribute</a></li>
|
||||
<li><a href="http://github.com/mitchellh/vagrant">code</a></li>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
layout: default
|
||||
title: Getting Started
|
||||
---
|
||||
## Installation
|
||||
|
||||
Vagrant is packaged as a [RubyGem](http://rubyforge.org/projects/rubygems). Note that
|
||||
vagrant is _not limited to just ruby-based projects_. On the contrary, vagrant does not
|
||||
care what tools or language your project uses, but the vagrant tool itself is written
|
||||
in Ruby and can be installed simply:
|
||||
|
||||
{% highlight bash %}
|
||||
$ gem install vagrant
|
||||
{% endhighlight %}
|
||||
|
||||
## Initialize Your Project
|
||||
|
||||
Once you've got vagrant installed, you'll want to initialize it for your project or
|
||||
projects. To do this, go to the root directory of your project, and do the following:
|
||||
|
||||
{% highlight bash %}
|
||||
$ vagrant init
|
||||
{% endhighlight %}
|
||||
|
||||
This will create an initial `Vagrantfile` in that directory, which is used not only
|
||||
to mark the root directory of your project but also to control every aspect of vagrant.
|
||||
37
index.md
37
index.md
|
|
@ -1,8 +1,37 @@
|
|||
---
|
||||
layout: default
|
||||
title: Welcome
|
||||
---
|
||||
Coming soon! For now, take a look at these pictures:
|
||||
Vagrant is a tool set out to **change the way web developers work**.
|
||||
|
||||
<img src="images/vagrant_looking.png" class="left" width="300px" />
|
||||
<img src="images/vagrant_holding.png" class="left" width="300px" />
|
||||
<img src="images/vagrant_chilling.png" class="left" width="300px" />
|
||||
Vagrant quickly and seamlessly builds and provisions virtual machines for
|
||||
development using [Sun's VirtualBox](http://www.virtualbox.org). Using vagrant,
|
||||
developers can continue to manage project files using their own system and editors,
|
||||
but all the servers, processes, etc. actually run within a virtualized environment.
|
||||
Vagrant allows ports to be forwarded so you can still test a web service, for example,
|
||||
by forwarding the virtual machine's port 80 to some port on the host machine and
|
||||
visiting it in any browser.
|
||||
|
||||
## Why Use Vagrant?
|
||||
|
||||
* **Get up and running without worrying about server setup** - Instead of spending
|
||||
hours setting up a development environment for a project, simply run
|
||||
`vagrant up` and get coding!
|
||||
* **Continue using your own editor and browser** - With shared folders and port forwarding,
|
||||
it feels exactly as if nothing has changed. You can still edit files using your favorite
|
||||
editor, and test the site using your favorite local tools.
|
||||
* **Avoid dependency hell** - Every project which uses vagrant has its own _unique and isolated virtual environment_,
|
||||
so the dependencies and configurations of multiple projects never collide.
|
||||
* **Cleanup when you're done** - When you're done working for the day, execute
|
||||
`vagrant down` and remove the virtual machine! No more web server, database, etc.
|
||||
processes running when they're not needed!
|
||||
* **Add developers quickly and easily** - For teams, adding developers to new projects
|
||||
is often a pain, since the new developer needs to learn how to setup all the
|
||||
different pieces of the application to get it running on his development machine.
|
||||
Forget about it! Just tell him to pull the latest code base from version control
|
||||
and run `vagrant up` and you're in business!
|
||||
|
||||
## Get Started!
|
||||
|
||||
Are you ready to use vagrant to revolutionize the way you work? Check out
|
||||
the [getting started guide](/docs/getting_started.html).
|
||||
Loading…
Reference in New Issue