<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -42,20 +42,20 @@ APP_ROOT/
 
 These scripts will be instance_eval'd in the context of the chef-deploy resource. This means that you will have certain commands and variables available to you in these hooks. For example:
 
-run &quot;echo 'release_path: #{release_path}' &gt;&gt; #{shared_path}/logs.log&quot;
-run &quot;echo 'current_path: #{current_path}' &gt;&gt; #{shared_path}/logs.log&quot;
-run &quot;echo 'shared_path: #{shared_path}' &gt;&gt; #{shared_path}/logs.log&quot;
-sudo &quot;echo 'sudo works' &gt;&gt; /root/sudo.log&quot;
+  run &quot;echo 'release_path: #{release_path}' &gt;&gt; #{shared_path}/logs.log&quot;
+  run &quot;echo 'current_path: #{current_path}' &gt;&gt; #{shared_path}/logs.log&quot;
+  run &quot;echo 'shared_path: #{shared_path}' &gt;&gt; #{shared_path}/logs.log&quot;
+  sudo &quot;echo 'sudo works' &gt;&gt; /root/sudo.log&quot;
 
 
 You have access to a run command and a sudo command. Both of these will run shell commands, run will run as your normal unix user that the app is deployed as and sudo will run as root for when you need more permissions.
 
 You will have variables like in capistrano:
 
-release_path: this is the full path to the current release:  /data/appname/releases/12345678
-shared_path: this is the path to the shared dir: /data/appname/shared
-current_path: this is the path to the currently symlinked release:  /data/appname/current
-node:  node is the full chef node object, this will have all of the JSON collected by ohai as well as any custom json you passed into your client run. THis way you can get at *any* data you have available to any of your chef recipes.
+  release_path: this is the full path to the current release:  /data/appname/releases/12345678
+  shared_path: this is the path to the shared dir: /data/appname/shared
+  current_path: this is the path to the currently symlinked release:  /data/appname/current
+  node:  node is the full chef node object, this will have all of the JSON collected by ohai as well as any custom json you passed into your client run. THis way you can get at *any* data you have available to any of your chef recipes.
 
 Using subversion:
 </diff>
      <filename>README.rdoc</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>ab690b10185b111c6a3b6c3e29ccdc1331ac74fa</id>
    </parent>
  </parents>
  <author>
    <name>Ezra Zygmuntowicz</name>
    <email>ez@engineyard.com</email>
  </author>
  <url>http://github.com/ezmobius/chef-deploy/commit/15c427720b840afffbf6c70fd2b8d57af173fa8a</url>
  <id>15c427720b840afffbf6c70fd2b8d57af173fa8a</id>
  <committed-date>2009-06-26T12:05:39-07:00</committed-date>
  <authored-date>2009-06-26T12:05:39-07:00</authored-date>
  <message>formatting for readme</message>
  <tree>50d373d5e4434420be829e387e64bb096da47cd6</tree>
  <committer>
    <name>Ezra Zygmuntowicz</name>
    <email>ez@engineyard.com</email>
  </committer>
</commit>
