From e38b5827ca1557ddcbb9b3e02e69bdc46970096f Mon Sep 17 00:00:00 2001
From: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Fri, 28 Jun 2013 00:04:41 -0400
Subject: [PATCH] website: doc veewee-to-packer

---
 .../templates/veewee-to-packer.html.markdown  | 60 +++++++++++++++++++
 website/source/layouts/docs.erb               |  1 +
 2 files changed, 61 insertions(+)
 create mode 100644 website/source/docs/templates/veewee-to-packer.html.markdown

diff --git a/website/source/docs/templates/veewee-to-packer.html.markdown b/website/source/docs/templates/veewee-to-packer.html.markdown
new file mode 100644
index 000000000..d52de7956
--- /dev/null
+++ b/website/source/docs/templates/veewee-to-packer.html.markdown
@@ -0,0 +1,60 @@
+---
+layout: "docs"
+page_title: "Convert Veewee Definitions to Packer Templates"
+---
+
+# Veewee-to-Packer
+
+If you are or were a user of [Veewee](https://github.com/jedi4ever/veewee),
+then there is an official tool called [veewee-to-packer](https://github.com/mitchellh/veewee-to-packer)
+that will convert your Veewee definition into an equivalent Packer template.
+Even if you're not a Veewee user, Veewee has a
+[large library](https://github.com/jedi4ever/veewee/tree/master/templates)
+of templates that can be readily used with Packer by simply converting them.
+
+## Installation and Usage
+
+Since Veewee itself is a Ruby project, so to is the veewee-to-packer
+application so that it can read the Veewee configurations. Install it using RubyGems:
+
+```
+$ gem install veewee-to-packer
+...
+```
+
+Once installed, usage is easy! Just point call `veewee-to-packer` pointed
+at the `definition.rb` file of any template. The converter will output
+any warnings or messages about the conversion. The example below converts
+a CentOS template:
+
+```
+$ veewee-to-packer templates/CentOS-6.4/definition.rb
+Success! Your Veewee definition was converted to a Packer
+template! The template can be found in the `template.json` file
+in the output directory: output
+
+Please be sure to run `packer validate` against the new template
+to verify settings are correct. Be sure to `cd` into the directory
+first, since the template has relative paths that expect you to
+use it from the same working directory.
+```
+
+***Voila!*** By default, `veewee-to-packer` will output a template that
+contains a builder for both VirtualBox and VMware. You can use the
+`-only` flag on `packer build` to only build one of them. Otherwise
+you can use the `--builder` flag on `veewee-to-packer` to only output
+specific builder configurations.
+
+## Limitations
+
+None, really. The tool will tell you if it can't convert a part of a
+template, and whether that is a critical error or just a warning.
+Most of Veewees functions translate perfectly over to Packer. There are
+still a couple missing features in Packer, but they're minimal.
+
+## Bugs
+
+If you find any bugs, please report them to the
+[veewee-to-packer issue tracker](https://github.com/mitchellh/veewee-to-packer).
+I haven't been able to exhaustively test every Veewee template, so there
+are certainly some edge cases out there.
diff --git a/website/source/layouts/docs.erb b/website/source/layouts/docs.erb
index c00993869..2582862e9 100644
--- a/website/source/layouts/docs.erb
+++ b/website/source/layouts/docs.erb
@@ -21,6 +21,7 @@
 			<li><a href="/docs/templates/provisioners.html">Provisioners</a></li>
 			<li><a href="/docs/templates/post-processors.html">Post-Processors</a></li>
 			<li><a href="/docs/templates/configuration-templates.html">Configuration Templates</a></li>
+			<li><a href="/docs/templates/veewee-to-packer.html">Veewee-to-Packer</a></li>
 		</ul>
 
 		<ul>