a-c-m
/
community.general
mirror of https://github.com/ansible-collections/community.general.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Reference Inventory & Patterns more 

Link to the Inventory & Patterns page in places where the Getting
Started guide refer to it, so that users unfamiliar with the
inventory syntax can easily familiarize themselves with it.
pull/4420/head
Buce 2013-05-24 14:27:39 -04:00
parent edb6a683f3
commit 563147d344
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docsite/latest/rst/gettingstarted.rst
View File

@ -45,7 +45,7 @@ also need:
Ansible) are not
switching over yet. However, some Linux distributions (Gentoo, Arch) may not have a
Python 2.X interpreter installed by default. On those systems, you should install one, and set
the 'ansible_python_interpreter' variable in inventory to point at your 2.X python. Distributions
the 'ansible_python_interpreter' variable in inventory (see :doc:`patterns`) to point at your 2.X python. Distributions
like Red Hat Enterprise Linux, CentOS, Fedora, and Ubuntu all have a 2.X interpreter installed
by default and this does not apply to those distributions. This is also true of nearly all
Unix systems. If you need to bootstrap these remote systems by installing Python 2.X,
@ -236,7 +236,7 @@ If you have python3 installed on Arch, you probably want to symlink python to py
$ sudo ln -sf /usr/bin/python2 /usr/bin/python
You should also set a 'ansible_python_interpreter' inventory variable for hosts that have python
You should also set a 'ansible_python_interpreter' inventory variable (see :doc:`patterns`) for hosts that have python
pointing to python3, so the right python can be found on the managed nodes.
Tagged Releases