From 070d2cc2a6906d9b90363cb88d1bf080b122e90f Mon Sep 17 00:00:00 2001
From: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Fri, 28 Jun 2013 08:37:13 -0400
Subject: [PATCH] website: vagrant boxes getting started

---
 .../parallel-builds.html.markdown             |  4 +-
 .../getting-started/vagrant.html.markdown     | 79 +++++++++++++++++++
 website/source/layouts/intro.erb              |  1 +
 3 files changed, 82 insertions(+), 2 deletions(-)
 create mode 100644 website/source/intro/getting-started/vagrant.html.markdown

diff --git a/website/source/intro/getting-started/parallel-builds.html.markdown b/website/source/intro/getting-started/parallel-builds.html.markdown
index c3f64210f..aa79eab9d 100644
--- a/website/source/intro/getting-started/parallel-builds.html.markdown
+++ b/website/source/intro/getting-started/parallel-builds.html.markdown
@@ -2,8 +2,8 @@
 layout: "intro"
 page_title: "Parallel Builds"
 prev_url: "/intro/getting-started/provision.html"
-next_url: "/intro/getting-started/next.html"
-next_title: "Next Steps"
+next_url: "/intro/getting-started/vagrant.html"
+next_title: "Vagrant Boxes"
 ---
 
 # Parallel Builds
diff --git a/website/source/intro/getting-started/vagrant.html.markdown b/website/source/intro/getting-started/vagrant.html.markdown
new file mode 100644
index 000000000..dcca867aa
--- /dev/null
+++ b/website/source/intro/getting-started/vagrant.html.markdown
@@ -0,0 +1,79 @@
+---
+layout: "intro"
+page_title: "Vagrant Boxes"
+prev_url: "/intro/getting-started/parallel-builds.html"
+next_url: "/intro/getting-started/next.html"
+next_title: "Next Steps"
+---
+
+# Vagrant Boxes
+
+Packer also has the ability to take the results of a builder (such as
+an AMI or plain VMware image) and turn it into a [Vagrant](http://www.vagrantup.com)
+box.
+
+This is done using [post-processors](/docs/templates/post-processors.html).
+These take an artifact created by a previous builder or post-processor and
+transforms it into a new one. In the case of the Vagrant post-processor, it
+takes an artifact from a builder and transforms it into a Vagrant box file.
+
+Post-processors are a generally very useful concept. While the example on
+this getting-started page will be creating Vagrant images, post-processors
+have many interesting use cases. For example, you can write a post-processor
+to compress artifacts, upload them, test them, etc.
+
+Let's modify our template to use the Vagrant post-processor to turn our
+AWS AMI into a Vagrant box usable with the [vagrant-aws plugin](https://github.com/mitchellh/vagrant-aws). If you followed along in the previous page and setup DigitalOcean,
+Packer can't currently make Vagrant boxes for DigitalOcean, but will be able
+to soon.
+
+## Enabling the Post-Processor
+
+Post-processors are added in the `post-processors` section of a template, which
+we haven't created yet. Modify your `example.json` template and add the section.
+Your template should look like the following:
+
+<pre class="prettyprint">
+{
+  "builders": [...],
+
+  "provisioners": [...],
+
+  "post-processors": ["vagrant"]
+}
+</pre>
+
+In this case, we're enabling a single post-processor named "vagrant". This
+post-processor is built-in to Packer and will create Vagrant boxes. You
+can always create [new post-processors](/docs/extend/post-processor.html), however.
+The details on configuring post-processors is covered in the
+[post-processors](/docs/templates/post-processors.html) documentation.
+
+Validate the configuration using `packer validate`.
+
+## Using the Post-Processor
+
+Just run a normal `packer build` and it will now use the post-processor.
+Since Packer can't currently make a Vagrant box for DigitalOcean anyways,
+I recommend passing the `-only=amazon-ebs` flag to `packer build` so it only
+builds the AMI. The command should look like the following:
+
+```
+$ packer build -only=amazon-ebs example.json
+```
+
+As you watch the output, you'll notice at the end in the artifact listing
+that a Vagrant box was made (by default at `packer_aws.box` in the current
+directory). Success!
+
+But where did the AMI go? When using post-processors, Vagrant removes
+intermediary artifacts since they're usually not wanted. Only the final
+artifact is preserved. This behavior can be changed, of course. Changing
+this behavior is covered [in the documentation](/docs/templates/post-processors.html).
+
+Typically when removing intermediary artifacts, the actual underlying
+files or resources of the artifact are also removed. For example, when
+building a VMware image, if you turn it into a Vagrant box, the files of
+the VMware image will be deleted since they were compressed into the Vagrant
+box. With creating AWS images, however, the AMI is kept around, since Vagrant
+needs it to function.
diff --git a/website/source/layouts/intro.erb b/website/source/layouts/intro.erb
index 038933fb1..8b1e6f18c 100644
--- a/website/source/layouts/intro.erb
+++ b/website/source/layouts/intro.erb
@@ -16,6 +16,7 @@
 			<li><a href="/intro/getting-started/build-image.html">Build an Image</a></li>
 			<li><a href="/intro/getting-started/provision.html">Provision</a></li>
 			<li><a href="/intro/getting-started/parallel-builds.html">Parallel Builds</a></li>
+			<li><a href="/intro/getting-started/vagrant.html">Vagrant Boxes</a></li>
 			<li><a href="/intro/getting-started/next.html">Next Steps</a></li>
 		</ul>
 	<% end %>