<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ansible-roles/bootstrap/tasks/main.yml, branch main</title>
<subtitle>Ansible roles shared between many of my playbooks
</subtitle>
<id>https://git.fennell.dev/ansible-roles/atom?h=main</id>
<link rel='self' href='https://git.fennell.dev/ansible-roles/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/ansible-roles/'/>
<updated>2026-09-09T21:17:34Z</updated>
<entry>
<title>Use bash as the default shell for admin</title>
<updated>2026-09-09T21:17:34Z</updated>
<author>
<name>Matthew Fennell</name>
<email>matthew@fennell.dev</email>
</author>
<published>2026-09-09T21:17:34Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/ansible-roles/commit/?id=954c8ecb4f1ff54f1097f92224447bf76293cf51'/>
<id>urn:sha1:954c8ecb4f1ff54f1097f92224447bf76293cf51</id>
<content type='text'>
ansible.builtin.user uses useradd's configured default shell if none is
specified - which on stock Debian systems, is /bin/sh. Choose a more sane
default with colours and reverse-search!

This is needed now as I'd like to run both bootstrap and munin-node against
both fennell.dev and search.fennell.dev, both of which were unmanaged in the
past. Now, at least the initial bootstrap and munin-node config will be managed
by ansible.
</content>
</entry>
<entry>
<title>Move bootstrap sources to their own subdirectory</title>
<updated>2026-09-09T20:50:33Z</updated>
<author>
<name>Matthew Fennell</name>
<email>matthew@fennell.dev</email>
</author>
<published>2026-09-09T20:48:42Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/ansible-roles/commit/?id=25db56f6241ae50feb54232e25f8203c1a450c7c'/>
<id>urn:sha1:25db56f6241ae50feb54232e25f8203c1a450c7c</id>
<content type='text'>
Since much of the setup (e.g. linter, hook, Makefile configuration) is
consistent between ansible roles, instead of having a separate repo per role
(as I initially planned), I'd prefer to have a single repo with all of the
roles that the playbooks can then pull from.

This is in preparation of adding a new munin-node role, following a similar
process to bootstrap.
</content>
</entry>
</feed>
