{"repo":"romantomjak/ansible-roles","free":true,"listed":false,"github":"https://github.com/romantomjak/ansible-roles","clone":"git clone https://github.com/romantomjak/ansible-roles.git","description":"Ansible roles and example playbooks for debian based hosts","language":"Jinja","stars":35,"topics":["ansible","devops","ansible-roles","debian","ansible-playbooks","consul","nomad","vault","traefik","playbook"],"license":"MIT","category":"deployment-docker-iac","readme_excerpt":"ansible Roles and playbooks for debian based hosts --- I'm following the philosophy that each role should just work without changing any of the arguments and while it's great for playing around, you shouldn't run this role in production without checking out the /defaults/main.yml and /README.md as that's where I describe what can be customized and offer advice and sample playbooks. How to use this I usually have a top-level directory named ansible in which I initialise this repo as a submodule in a folder named common : This way I can have roles that are common to all my projects - like docker or firewall + project specific roles and playbooks. In this setup it's imperative to have the ansible.cfg file pointing to our common roles: Useful commands How to initialise Git submodule On recent Git versions it's enough with: and when the upstream changes and you would like to pull the latest changes: Syntax check Run against a single host Play needs to have hosts: all , then run: Note the comma (,) at the end; this signals that it's a list, not a file. Notes - Ansible Coding Conventions License MIT","default_branch":null,"files":null,"tree":[],"storefront":"/r/romantomjak","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/romantomjak/ansible-roles/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}