gregandev/rpi-ansible
1
0
Fork 0
mirror of https://github.com/ruanbekker/rpi-ansible.git synced 2025-04-20 09:11:45 +02:00
Code Issues Projects Releases Wiki Activity

acknowledge problems in using venv on 9.13

Browse Source
This commit is contained in:
Glenn K. Lockwood 2020-07-27 16:22:00 -07:00
parent 9f0e9d1947
commit be1f6950ef
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -21,10 +21,17 @@ playbook relies on Ansible 2.8 or newer, which means you can no longer use
# Make sure that pip will install into our virtualenv # Make sure that pip will install into our virtualenv
(ansible_env) $ which pip (ansible_env) $ which pip
/home/pi/src/git/rpi-ansible/ansible/bin/pip /home/pi/src/git/rpi-ansible/ansible/bin/pip
# Install ansible and any other requirements # Install ansible and any other requirements
(ansible_env) $ pip install -r requirements.txt (ansible_env) $ pip install -r requirements.txt
Note that the Python 3.5 that ships with Debian 9.13 doesn't install pip when
`-m venv` is used as above. It may be easier to simply use
$ pip3 install --user ansible
which pollutes your login Python environment, but is better than nothing.
## Configuration ## Configuration
The `macaddrs` structure in _roles/common/vars/main.yml_ maps the MAC address of The `macaddrs` structure in _roles/common/vars/main.yml_ maps the MAC address of
@ -40,7 +47,7 @@ structure in `roles/common/vars/users.yml.example`. You can/should
Then run the playbook: Then run the playbook:
(ansible_env) $ sudo $(which ansible-playbook) --ask-vault-pass ./local.yml (ansible_env) $ ansible-playbook --ask-vault-pass --become --become-user root --ask-become-pass ./local.yml
The playbook will self-discover its settings, then idempotently configure the The playbook will self-discover its settings, then idempotently configure the
Raspberry Pi. Raspberry Pi.