Rebuild

bestpractices.html

@@ -225,7 +225,7 @@ will require <cite>handlers</cite>, <cite>tasks</cite>, and <cite>templates</cit
 - hosts: webservers
   user: root
 
-  vars_files
+  vars_files:
     - ../global_vars.yml
     - vars/main.yml
   tasks:
@@ -237,7 +237,7 @@ will require <cite>handlers</cite>, <cite>tasks</cite>, and <cite>templates</cit
 are contained in &#8216;acme/handlers/main.yml&#8217;.  As a reminder, handlers are mostly just used to notify services to restart
 when things change, and these are described in <a class="reference internal" href="playbooks.html"><em>Playbooks</em></a>.</p>
 <p>Including more than one setup file or more than one handlers file is of course legal.</p>
-<p>Having playbooks be able to include other playbooks is coming in release 0.5.</p>
+<p>Having playbooks be able to include other playbooks is coming in a future release. See Issue 538.</p>
 <p>Until then, to manage your entire site, simply execute all of your playbooks together, in the order desired.
 You don&#8217;t have to do this though. It&#8217;s fine to select sections of your infrastructure to manage at a single time.
 You may wish to construct simple shell scripts to wrap calls to ansible-playbook.</p>

modules.html

@@ -251,12 +251,17 @@ Defaults to &#8216;no&#8217;.</li>
 <ul class="simple">
 <li>Corresponds to the -t option for apt, and sets pin priorities</li>
 </ul>
+<p><em>install-recommends</em>: (devel branch now, part of ansible 0.6 later)</p>
+<ul class="simple">
+<li>Corresponds to the &#8211;no-install-recommends option for apt. Defaults to &#8216;yes&#8217;, which means install the recommended packages the same way APT does by default. Set this to &#8216;no&#8217; to add the option not to install recommended packages.</li>
+</ul>
 <p>Example action from Ansible <a class="reference internal" href="playbooks.html"><em>Playbooks</em></a>:</p>
 <div class="highlight-python"><pre>apt pkg=foo update-cache=yes
 apt pkg=foo state=removed
 apt pkg=foo state=installed
 apt pkg=foo=1.00 state=installed
-apt pkg=nginx state=latest default-release=squeeze-backports update-cache=yes</pre>
+apt pkg=nginx state=latest default-release=squeeze-backports update-cache=yes
+apt pkg=openjdk-6-jdk state=latest install-recommends=no</pre>
 </div>
 </div>
 <div class="section" id="assemble">

patterns.html

@@ -326,7 +326,6 @@ database_server: storage.example.org</pre>
 is an excellent way to track changes to your inventory and host variables.</p>
 <p>Tip: If you ever have two python interpreters on a system, set a variable called &#8216;ansible_python_interpreter&#8217; to
 the Python interpreter path you would like to use.</p>
-<p>Tip: Be sure to start any YAML file with the YAML record designator <tt class="docutils literal"><span class="pre">---</span></tt> on the first line.</p>
 </div>
 <div class="section" id="yaml-inventory">
 <h2>YAML Inventory<a class="headerlink" href="#yaml-inventory" title="Permalink to this headline">¶</a></h2>