mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Sphinx formatting.
This commit is contained in:
parent
ade46e9aab
commit
715a07d200
4 changed files with 6 additions and 8 deletions
|
@ -49,7 +49,7 @@ IT tasks in the core distribution. This means modules are well up-to-date and y
|
||||||
that will work on your platform. You may think of the module library as a toolbox full of useful system management tools,
|
that will work on your platform. You may think of the module library as a toolbox full of useful system management tools,
|
||||||
and playbooks as the instructions for buildilng something using those tools.
|
and playbooks as the instructions for buildilng something using those tools.
|
||||||
|
|
||||||
.. toctree:
|
.. toctree::
|
||||||
modules
|
modules
|
||||||
|
|
||||||
.. _overview:
|
.. _overview:
|
||||||
|
@ -130,7 +130,7 @@ installed using Ansible playbooks!
|
||||||
Detailed Guides
|
Detailed Guides
|
||||||
```````````````
|
```````````````
|
||||||
|
|
||||||
This section is new and evolving. The idea here is explore particular use cases in greater depth and provide a more "top down" explanation of some basic features::
|
This section is new and evolving. The idea here is explore particular use cases in greater depth and provide a more "top down" explanation of some basic features.
|
||||||
|
|
||||||
.. toctree::
|
.. toctree::
|
||||||
:maxdepth: 1
|
:maxdepth: 1
|
||||||
|
|
|
@ -1,11 +1,9 @@
|
||||||
.. _patterns:
|
Patterns
|
||||||
|
++++++++
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
:depth: 2
|
:depth: 2
|
||||||
|
|
||||||
Patterns
|
|
||||||
++++++++
|
|
||||||
|
|
||||||
Patterns in Ansible are how we decide which hosts to manage. This can mean what hosts to communicate with, but in terms
|
Patterns in Ansible are how we decide which hosts to manage. This can mean what hosts to communicate with, but in terms
|
||||||
of :doc:`playbooks` it actually means what hosts to apply a particular configuration or IT process to.
|
of :doc:`playbooks` it actually means what hosts to apply a particular configuration or IT process to.
|
||||||
|
|
||||||
|
|
|
@ -92,7 +92,7 @@ For each play in a playbook, you get to choose which machines in your infrastruc
|
||||||
to target and what remote user to complete the steps (called tasks) as.
|
to target and what remote user to complete the steps (called tasks) as.
|
||||||
|
|
||||||
The `hosts` line is a list of one or more groups or host patterns,
|
The `hosts` line is a list of one or more groups or host patterns,
|
||||||
separated by colons, as described in the :ref:`intro_patterns`
|
separated by colons, as described in the :doc:`intro_patterns`
|
||||||
documentation. The `remote_user` is just the name of the user account::
|
documentation. The `remote_user` is just the name of the user account::
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
|
@ -669,7 +669,7 @@ The contents of each variables file is a simple YAML dictionary, like this::
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
It's also possible to keep per-host and per-group variables in very
|
It's also possible to keep per-host and per-group variables in very
|
||||||
similar files, this is covered in :ref:`patterns`.
|
similar files, this is covered in :ref:`intro_patterns`.
|
||||||
|
|
||||||
.. _passing_variables_on_the_command_line:
|
.. _passing_variables_on_the_command_line:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue