website: debugging section

website/source/docs/other/debugging.html.markdown

@@ -0,0 +1,24 @@
+---
+layout: "docs"
+---
+
+# Debugging Packer
+
+Packer strives to be stable and bug-free, but issues inevitably arise where
+certain things may not work entirely correctly, or may not appear to work
+correctly. In these cases, it is sometimes helpful to see more details about
+what Packer is actually doing.
+
+Packer has detailed logs which can be enabled by setting the `PACKER_LOG`
+environmental variable to any value. This will cause detailed logs to appear
+on stderr. The logs contain log messages from Packer as well as any plugins
+that are being used. Log messages from plugins are prefixed by their application
+name.
+
+Note that because Packer is highly parallelized, log messages sometimes
+appear out of order, especially with respect to plugins. In this case,
+it is important to pay attention to the timestamp of the log messages
+to determine order.
+
+If you find a bug with Packer, please include the detailed log by using
+a service such as [gist](http://gist.github.com).

website/source/layouts/docs.erb

@@ -46,10 +46,14 @@
 							<li><a href="/docs/builders/vmware.html">VMware</a></li>
 							<li><a href="/docs/builders/custom.html">Custom</a></li>
 
-							<li class="nav-header">Provisioners</a></li>
+							<li class="nav-header">Provisioners</li>
 							<li><a href="#">Shell Scripts</a></li>
 							<li><a href="#">Custom</a></li>
 
+							<li class="nav-header">Other</li>
+							<li><a href="#">Core Configuration</a></li>
+							<li><a href="/docs/other/debugging.html">Debugging</a></li>
+
 							<li class="nav-header">Extend Packer</li>
 							<li><a href="/docs/extend/plugins.html">Packer Plugins</a></li>
 							<li><a href="/docs/extend/developing-plugins.html">Developing Plugins</a></li>