I’ve never really used ansible before, and rarely get to play with freebsd so when I needed to setup a new IRC bouncer I decided what better chance than now to have a play. Although there are some built-in ansible modules for working with the ports system (Which is what we are going to use to install znc), they aren’t yet complete enough to bootstrap a server from scratch. We first need to setup our local computer to allow us to connect to the freebsd server.

Despite having a big warning at the bottom of the docroot/sites/default/settings.php file telling you not to add additional settings to that file. The BLT documentation does little do say what the recommended way of conditionally including *.settings.php files depending on environment variables or some other decider. Normally, you would do it by adding code to the effect of the below to docroot/sites/default/settings.php but since there is such a direct warning not to in the BLT version, I needed to find a better way:

Why did we move away from the logical threading to the new gmail-and-everyone-else style? The problem with emails is that you can reply to any email in a ’thread’. Seriously? You can even reply twice to the same email and create a new branch of replies. The new ‘conversation’ style of gmail and others just doesn’t take this into account. Admittedly, it works OK when everyone is using the conversation style, and only ever replies to the very latest email.

Project Overview I recently moved into a new place which has historically had issues with mould growth. As part of the preventative measures, I’m planning on building a set of temperature and humidity monitors that I can place around the house and keep track of how at risk rooms are over time. They need to be reasonably small, but can be mains-powered as there will be an outlet in every room I plan to monitor.

Kubernetes can be a daunting topic even to those well versed in docker. There are so many layers of abstraction on top of abstraction and new terms that it can seem like you need to learn a completely new dictionary just to understand the documenation. This series hopes to change that fact by assuming the only knowledge the reader has is of docker. We will assume that you know about: