iman(8) Ansible on Thunix man(8) null.host 1 i null.host 1 iNAME null.host 1 i Ansible on Thunix - how we manage the server null.host 1 i null.host 1 iSYNOPSIS null.host 1 i ansible-pull null.host 1 i null.host 1 iDESCRIPTION null.host 1 i We use ansible to manage the servers running the systems null.host 1 i and services for Thunix. Ansible consists of a "playbook" null.host 1 i of YAML files, that declare the state of the system. null.host 1 i null.host 1 i The first step is to clone the repo used to manage the en‐ null.host 1 i vironment: null.host 1 i null.host 1 i git clone git@ttm.sh:thunix/ansible.git (You will need a null.host 1 i tidegit account for this, and a key loaded into your ac‐ null.host 1 i count there) null.host 1 i null.host 1 i From there, the typical github-type workflow is used: null.host 1 i null.host 1 i * Create a local branch, to track your issue's changes. null.host 1 i null.host 1 i * Commit changes to your local branch. null.host 1 i null.host 1 i * Send a URI pointing to your repo, with branch name to null.host 1 i someone with merge permissions null.host 1 i null.host 1 i Inside of the tildegit interface: null.host 1 i null.host 1 i * Create a new branch, selecting option to create a branch null.host 1 i and pull request null.host 1 i null.host 1 i * Make changes in your branch null.host 1 i null.host 1 i * Update PR null.host 1 i null.host 1 i * Wait for someone to merge your changes null.host 1 i null.host 1 i Hourly, a job runs that pulls the latest version of the null.host 1 i repo, and the runs ansible-playbook against the playbook. null.host 1 i A sudoer can manually run this job, if desired, and it's null.host 1 i located at /etc/cron.hourly/ansible-pull. null.host 1 i null.host 1 iSEE ALSO null.host 1 i tildegit.org(8), git(8), ansible-playbook(8) null.host 1 i null.host 1 iBUGS null.host 1 i No known bugs. null.host 1 i null.host 1 iAUTHOR null.host 1 i Uber Geek (ubergeek@thunix.net) null.host 1 i null.host 1 i1.1 19 February 2019 man(8) null.host 1 .