I’ve given myself a personal goal of creating 100 ansible playbooks, I suppose roles would also count. The destination is essentially accomplishing 100 goals with ansible. These are what I’ve already accomplished. blocky.yml install_disable_usb_wake.yml install_sshd_config.yml install_sudo.yml lynis.yml podman.yml promtail.yml run_updates.yml Overall not terribly complex roles, most of them have hardcoded defaults but that’ll probably get resolved when the existing playbooks get converted to roles. Most recently I made a playbook that setup and configured blocky-dns which would be my 8th playbook.

Spent a good part of the morning working on writing an Ansible playbook to install and setup promtail on a new server, adding it to the central logging setup. At first I started manually downloading the binary and manually installing it when I remembered I wanted to work on using ansible more. So I stopped where I was and started over again except this time electing to use the power of automation.

When done working on my desktop I suspend it, either through the Cinnamon panel or via systemctl suspend. But it had an issue. I would frequently come downstairs to find it on. The monitors with their familiar glow lighting up the room. My desktop running Linux Mint had a problem. Some initial diagnosis lead me to finding out that the issue was that the keyboard and mouse, paired with the lovely kitties were waking it from it’s slumber.

While changing what source image a docker container in unRaid was using, the Docker managment service encountered an error. The error itself I forgot to write down. But what is normally a typical process of “download new image, stop old container. create new container, cleanup old image.” was interrupted and it left the container in a down state. This wasn’t good primarily because I am lazy and didn’t want to spend the mental power and try to come up with what the previous config options were so there can be no change except what image is being used.

One of the services my unRaid box runs is a borgbackup server (which is secretly just an SSH server with a forced command). As a check to make sure the important repos are indeed getting backed up to I’ve got a script running daily via the User Scripts Plugin. It’s a pretty simple script, all it does is check when the files in certain target repos have last been written to.