1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00

Typo + fix header depth

This commit is contained in:
Michael DeHaan 2012-04-19 10:45:41 -04:00
parent bbde1bdfa0
commit bc0980496c
5 changed files with 29 additions and 29 deletions

View file

@ -130,16 +130,14 @@ s.parentNode.insertBefore(ga, s);
<li><a class="reference internal" href="#">The Future Is Now</a></li>
<li><a class="reference internal" href="#innovative-multi-node-control">Innovative Multi-node Control</a></li>
<li><a class="reference internal" href="#deployment-and-configuration-unified">Deployment and Configuration, Unified</a></li>
<li><a class="reference internal" href="#simple-secure-by-default">Simple &amp; Secure By Default</a><ul>
<li><a class="reference internal" href="#simple-secure-by-default">Simple &amp; Secure By Default</a></li>
<li><a class="reference internal" href="#architecture">Architecture</a></li>
<li><a class="reference internal" href="#features">Features</a></li>
<li><a class="reference internal" href="#resources">Resources</a></li>
<li><a class="reference internal" href="#contents">Contents</a><ul>
</ul>
</li>
<li><a class="reference internal" href="#about-the-author">About the Author</a></li>
</ul>
</li>
<li><a class="reference internal" href="#presented-by">Presented By...</a></li>
</ul>
</span>
</li>
@ -205,12 +203,13 @@ of these other tools, which can, more or less, turn into a botnet. Our security
crypto code altogether, and rely on the most secure part of the Linux/Unix subsystem that your machines are already using. There is no PKI subsystem to maintain, which can be a frequent source of problems, particularly when reinstalling or migrating
hosts.</p>
<p>Systems management doesn&#8217;t have to be complicated. Ansible&#8217;s docs will remain short &amp; simple, and the source will be blindingly obvious. We&#8217;ve learned well from &#8220;Infrastructure is Code&#8221;. Infrastructure should be easy and powerful to command, but it should not look like code, lest it acquire the disadvantages of a software project &#8211; bugs, complexity, and overhead. Infrastructure configurations should be simple, easy to develop, and easy to audit.</p>
</div>
<div class="section" id="architecture">
<h2>Architecture<a class="headerlink" href="#architecture" title="Permalink to this headline"></a></h2>
<h1>Architecture<a class="headerlink" href="#architecture" title="Permalink to this headline"></a></h1>
<div align="center" class="align-center"><img alt="&quot;Architecture Diagram&quot;" class="align-center" src="http://ansible.github.com/ansible_arch2.jpg" style="width: 800px;" /></div>
</div>
<div class="section" id="features">
<h2>Features<a class="headerlink" href="#features" title="Permalink to this headline"></a></h2>
<h1>Features<a class="headerlink" href="#features" title="Permalink to this headline"></a></h1>
<ul class="simple">
<li>Dead simple setup</li>
<li>Super fast &amp; parallel by default</li>
@ -227,7 +226,7 @@ hosts.</p>
</ul>
</div>
<div class="section" id="resources">
<h2>Resources<a class="headerlink" href="#resources" title="Permalink to this headline"></a></h2>
<h1>Resources<a class="headerlink" href="#resources" title="Permalink to this headline"></a></h1>
<p>Your ideas and contributions are welcome. We&#8217;re also happy to help
you with questions about Ansible.</p>
<ul class="simple">
@ -248,7 +247,7 @@ Email: <input type=text name=email>&nbsp;&nbsp;<input type=submit name="sub" val
</form>
<br/></div>
<div class="section" id="contents">
<h2>Contents<a class="headerlink" href="#contents" title="Permalink to this headline"></a></h2>
<h1>Contents<a class="headerlink" href="#contents" title="Permalink to this headline"></a></h1>
<div class="toctree-wrapper compound">
<ul>
<li class="toctree-l1"><a class="reference internal" href="gettingstarted.html">Downloads &amp; Getting Started</a><ul>
@ -265,7 +264,7 @@ Email: <input type=text name=email>&nbsp;&nbsp;<input type=submit name="sub" val
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="patterns.html">The Inventory File, Patterns, and Groups</a><ul>
<li class="toctree-l2"><a class="reference internal" href="patterns.html#baisc-inventory-file-format">Baisc Inventory File Format</a></li>
<li class="toctree-l2"><a class="reference internal" href="patterns.html#basic-inventory-file-format">Basic Inventory File Format</a></li>
<li class="toctree-l2"><a class="reference internal" href="patterns.html#selecting-targets">Selecting Targets</a></li>
<li class="toctree-l2"><a class="reference internal" href="patterns.html#advanced-inventory-file-format">Advanced Inventory File Format</a></li>
</ul>
@ -372,11 +371,11 @@ Email: <input type=text name=email>&nbsp;&nbsp;<input type=submit name="sub" val
</ul>
</div>
</div>
<div class="section" id="about-the-author">
<h2>About the Author<a class="headerlink" href="#about-the-author" title="Permalink to this headline"></a></h2>
<p>Ansible was originally developed by <a class="reference external" href="http://michaeldehaan.net">Michael DeHaan</a> (<a class="reference external" href="http://twitter.com/#!/laserllama">&#64;laserllama</a>), a Raleigh, NC
based software developer and architect. He created the popular
DevOps program <a class="reference external" href="http://cobbler.github.com/">Cobbler</a>.
<div class="section" id="presented-by">
<h1>Presented By...<a class="headerlink" href="#presented-by" title="Permalink to this headline"></a></h1>
<p>Ansible was created and is run by <a class="reference external" href="http://michaeldehaan.net">Michael DeHaan</a> (<a class="reference external" href="http://twitter.com/#!/laserllama">&#64;laserllama</a>), a Raleigh, NC
based software developer and architect, who also created the popular
DevOps install server <a class="reference external" href="http://cobbler.github.com/">Cobbler</a>.
Cobbler is used to deploy mission critical systems all over the
planet, in industries ranging from massively multiplayer gaming, core
internet infrastructure, finance, chip design, and more. Michael also
@ -385,7 +384,6 @@ orchestrate systems in lots of diverse places. He&#8217;s worked on systems
software for IBM, Motorola, Red Hat&#8217;s Emerging Technologies Group,
Puppet Labs, and rPath. Reach Michael by email <a class="reference external" href="mailto:michael&#46;dehaan&#37;&#52;&#48;gmail&#46;com">here</a>.</p>
</div>
</div>
</div>

View file

@ -129,7 +129,7 @@ s.parentNode.insertBefore(ga, s);
class="dropdown-toggle">Page</a>
<span class="localtoc"><ul>
<li><a class="reference internal" href="#">The Inventory File, Patterns, and Groups</a><ul>
<li><a class="reference internal" href="#baisc-inventory-file-format">Baisc Inventory File Format</a></li>
<li><a class="reference internal" href="#basic-inventory-file-format">Basic Inventory File Format</a></li>
<li><a class="reference internal" href="#selecting-targets">Selecting Targets</a></li>
<li><a class="reference internal" href="#advanced-inventory-file-format">Advanced Inventory File Format</a></li>
</ul>
@ -163,8 +163,8 @@ s.parentNode.insertBefore(ga, s);
<p>Ansible works against multiple systems in your infrastructure at the
same time. It does this by selecting portions of systems listed in
Ansible&#8217;s inventory file, which defaults to /etc/ansible/hosts.</p>
<div class="section" id="baisc-inventory-file-format">
<span id="inventoryformat"></span><h2>Baisc Inventory File Format<a class="headerlink" href="#baisc-inventory-file-format" title="Permalink to this headline"></a></h2>
<div class="section" id="basic-inventory-file-format">
<span id="inventoryformat"></span><h2>Basic Inventory File Format<a class="headerlink" href="#basic-inventory-file-format" title="Permalink to this headline"></a></h2>
<p>The format for /etc/ansible/hosts looks like this:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">mail</span><span class="o">.</span><span class="n">example</span><span class="o">.</span><span class="n">com</span>

View file

@ -52,7 +52,7 @@ Systems management doesn't have to be complicated. Ansible's docs will remain s
Architecture
============
````````````
.. image:: http://ansible.github.com/ansible_arch2.jpg
:alt: "Architecture Diagram"
@ -60,7 +60,7 @@ Architecture
:align: center
Features
========
````````
* Dead simple setup
* Super fast & parallel by default
@ -77,7 +77,7 @@ Features
Resources
=========
`````````
Your ideas and contributions are welcome. We're also happy to help
you with questions about Ansible.
@ -103,7 +103,7 @@ you with questions about Ansible.
Contents
========
````````
.. toctree::
:maxdepth: 3
@ -118,12 +118,12 @@ Contents
moduledev
faq
About the Author
================
Presented By...
```````````````
Ansible was originally developed by `Michael DeHaan <http://michaeldehaan.net>`_ (`@laserllama <http://twitter.com/#!/laserllama>`_), a Raleigh, NC
based software developer and architect. He created the popular
DevOps program `Cobbler <http://cobbler.github.com/>`_.
Ansible was created and is run by `Michael DeHaan <http://michaeldehaan.net>`_ (`@laserllama <http://twitter.com/#!/laserllama>`_), a Raleigh, NC
based software developer and architect, who also created the popular
DevOps install server `Cobbler <http://cobbler.github.com/>`_.
Cobbler is used to deploy mission critical systems all over the
planet, in industries ranging from massively multiplayer gaming, core
internet infrastructure, finance, chip design, and more. Michael also
@ -131,3 +131,5 @@ helped co-author `Func <http://fedorahosted.org/func/>`_, a precursor to Ansible
orchestrate systems in lots of diverse places. He's worked on systems
software for IBM, Motorola, Red Hat's Emerging Technologies Group,
Puppet Labs, and rPath. Reach Michael by email `here <mailto:michael.dehaan@gmail.com>`_.

View file

@ -9,7 +9,7 @@ Ansible's inventory file, which defaults to /etc/ansible/hosts.
.. _inventoryformat:
Baisc Inventory File Format
Basic Inventory File Format
+++++++++++++++++++++++++++
The format for /etc/ansible/hosts looks like this::

File diff suppressed because one or more lines are too long