<h1>Best Practices<aclass="headerlink"href="#best-practices"title="Permalink to this headline">¶</a></h1>
<p>Here are some tips for making the most of Ansible.</p>
<divclass="section"id="always-mention-state">
<h2>Always Mention State<aclass="headerlink"href="#always-mention-state"title="Permalink to this headline">¶</a></h2>
<p>The ‘state’ parameter is optional to a lot of modules. Whether state=present or state=absent, it’s always
best to leave that parameter in your playbooks to make it clear, especially as some modules support additional
states.</p>
</div>
<divclass="section"id="group-by-roles">
<h2>Group By Roles<aclass="headerlink"href="#group-by-roles"title="Permalink to this headline">¶</a></h2>
<p>A system can be in multiple groups. See <aclass="reference internal"href="patterns.html"><em>Inventory & Patterns</em></a>. Having groups named after things like
Ansible is used by all sorts of organizations from hosted web applications, media companies, consultancies, and ISVs. Some of these include:
Ansible is used by all sorts of organizations from hosted web applications, media companies, universities, consultancies, and ISVs -- all over the world. Some of these users include:
<h1>Who Uses Ansible<aclass="headerlink"href="#who-uses-ansible"title="Permalink to this headline">¶</a></h1>
<p>Ansible is used by all sorts of organizations from hosted web applications, media companies, consultancies, and ISVs. Some of these include:</p>
<p>Ansible is used by all sorts of organizations from hosted web applications, media companies, universities, consultancies, and ISVs – all over the world. Some of these users include:</p>