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

Fixing a couple more internal doc links.

Browse source
This commit is contained in:
John Callender 2012-05-15 18:16:32 -07:00
parent b896157d61
commit b243b8dcbf
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
rst/bestpractices.rst
View file

@ -42,7 +42,7 @@ Playbooks should be organized like this::
stop.yml
Any directories or files not needed can be omitted. Not all modules may require `vars` or `files` sections, though most
will require `handlers`, `tasks`, and `templates`. To review what each of these sections do, see ref:`playbooks` and ref:`playbooks2`.
will require `handlers`, `tasks`, and `templates`. To review what each of these sections do, see :doc:`playbooks` and :doc:`playbooks2`.
The acme/setup.yml playbook would be as simple as::

2
rst/faq.rst
View file

@ -173,7 +173,7 @@ them probably isn't appropriate, which is why ansible-pull exists.
This tool is designed for running out of git and cron, and can scale to any
number of hosts. Ansible-pull uses local connections versus SSH, but can be
easily bootstrapped or reconfigured just using SSH. There is more information
available about this in the ref:`playbooks2` section. The self-bootstrapping
available about this in the :doc:`playbooks2` section. The self-bootstrapping
and ease of use are ansible are still retained, even when switching to the pull
model.