Hi Max, On 2016-03-19 04:34, Max Kraszewski wrote: > [...] but I'd like a little more organization > So I decided to create a *playbooks* folder and move them in some > subdirectories inside.
Isn't a vast number of tasks in the project's main folder a sign that you aren't using roles enough? > Following this repository > <https://github.com/enginyoyen/ansible-best-practises> guideline, I created > an ansible.cfg file with role_path=../roles roles_path not role_path -- but I guess it's just a typo in the mail. http://docs.ansible.com/ansible/playbooks_roles.html suggests to use a central location for all roles across projects and use roles_path with one (absolute) path: " In Ansible 1.4 and later you can configure a roles_path to search for roles. Use this to check all of your common roles out to one location, and share them easily between multiple playbook projects. See Configuration file for details about how to set this up in ansible.cfg. " Using recommendations and best practices from ansible.com has the advantage that on-boarding others is relatively easy. You'll have a single source to point them to. Regards, Benjamin -- FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html vox: +49 3641 9 44323 | fax: +49 3641 9 44321 -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/56EDF38F.4070301%40uni-jena.de. For more options, visit https://groups.google.com/d/optout.
