Last week JSONFeed, an RSS/Atom alternative using JSON, was introduced and to me that seemed like a good excuse to play around with Hugo's new Output Formats.

A couple of weeks ago, I mentioned that I would like to learn more about Google Cloud Platform. Two days later I learned that there would be a Google Cloud OnBoard session in Melbourne. This happened recently, so I put on an AWS shirt and went to check it out.

As you may be aware, I sent updates of this site out by email. Since the very start I've used Convertkit for this, but this was getting too expensive. However, it was the only email service I found that will immediately send an email instead of on a schedule. So, I had to automate this.

As I just returned from a holiday to China, I wanted to share some of my observations about technology there. This is only meant as a general overview and is completely based on what I saw around me.

Almost 2 months ago, AWS announced a serverless chatbot competition. As I happen to have one of those lying around I decided to enter this competition.

When using Docker containers to trigger Ansible configuration, you can run into an issue regarding Docker's virtual filesystem and SSH sockets. This shows how I worked around that problem.

While following my own steps for resizing an EBS volume, I discovered that Redhat-based systems require more.

Because Redhat-based OSes are slightly different from Debian-based ones, I ran into some issues provisioning an AMI with Ansible and Packer. This article is to ensure I can find the solution quickly in the future.

Pipelines seems to be almost as popular as machine learning right now and earlier this week Atlassian announced that Bitbucket now has them built in as well. Or rather, it's in beta. Naturally, I was interested so I decided to take it for a spin. This article shows how I set it up for one of my existing projects, and I'll go into the good parts and the limitations.

In my ongoing quest for automating all deployment related matters, I discovered I needed a way to pull in single files from S3 for my Wercker builds. As I couldn't find a step for that, I built one.

While Aqua neatly makes the initial setup for my Lambda functions easier, that still left me with the deployments. In order to deal with that, I therefore made a simple deployment step for Wercker. I'll first go over how to use it, before showing how it works.

Last month I wrote about the installation script I built for Igor, but as I started writing more Lambda functions recently I realized that I needed that same functionality in a more easily accessible way. So I created Aqua to do this for me.

Over the past couple of weeks I've written several articles about the things that support Igor, from deployments to installation, but I haven't written much about how it actually works yet. This article aims to rectify that.

At the Docker birthday event last week I decided that instead of working on the Birthday Challenge I would make Igor work on Docker as well. That meant I need to deploy two versions from a single build however, and in this article I'll explain how that works.

When I set up Igor in Lambda for the first time, I mostly followed the directions as provided in a Lambda template. This template has a description of all the steps that need to be taken, but to be honest it's a bit unwieldy. So I created a script to do this for me.