Linux Administration Cookbook

There's more...

It might seem like overkill to put together a playbook for the sake of one role, but the beauty of playbooks is that they're not bound to one role. You can include as many as you want in the list within the playbook.yml file, and, as long as they don't conflict with each other, you should have a very smooth Ansible experience.

Take a look at this playbook.yml file instead:

$ cat <<HERE > playbook.yml---- hosts: all  roles:  - geerlingguy.java  - geerlingguy.docker  - geerlingguy.apacheHERE

We also used galaxy in a very specific way, using ansible-galaxy to install the role from the internet first. You could also include a requirements.yml file with your code, which ansible-galaxy is able to read so that it might download any listed ...