Roles and Galaxy

Part of the Ansible course

Sooner or later you end up with two playbooks that both install nginx, both drop the same config template, and both restart the service afterward, because two different projects both happened to need a web server. Copy the tasks from one playbook into the other and you now have two copies of the same logic to keep in sync, and the first time you fix a bug in one copy and forget the other, they quietly drift apart.

A role is a reusable bundle of tasks, templates, and default values that you can drop into any playbook by name, instead of writing the underlying logic out again for every project that happens to need the same thing. Think of it the way a construction crew thinks of a prefabricated wall panel: the panel was designed once, built once, tested once, and now it gets bolted onto whichever building needs a wall in that...