Blog Posts

Our migration from a home rolled Docker builder to using Docker's Buildkit and Buildx tools.

If you've ever encountered the above message when logging into Docker and thought to yourself 'Well it’s unencrypted but it works... I'll deal with it another day' then we've got something in common.

I've been playing around with Actions ever since and one of my new projects, a Ruby Gem, didn't have any form of CI as of this morning. I set out to create an Action that would run the tests for the gem and produce coverage results via SimpleCov.

Recently, I started working on a new side project in Elixir and I think I've finally found something I'm going to stick with; a service where we are required to add a label to our Pull Requests and a Slack channel is notified that the PR is ready to be reviewed

I started reminiscing on all I had learned over the past ten years and decided I wanted to write a brief summary of my journey to becoming a Software Engineer and what I hope to accomplish moving forward.

Recently, I decided that one of my goals for 2019 was to familiarize myself more with Docker. I've been exposed to using Docker for the past couple of years, but I don't use it on a day to day basis.

I realized that we are always using Ruby Alpine images, and not the base Ruby image. I wanted to standardize the Dockerfiles I had written at work and here for the blog so I decided to look into what it would take to do so.

Set up a testing environment that can be run locally and in a repeatable fashion for continuous integration

The process I went through to figure out what was needed; I believe it is good exercise in understanding how to follow code to and understanding what it takes to re-implement functionality.

Instead of having to create a Rails application and install the gem to connect to the database to test your models, we can create local database for only the gem by adding ActiveRecord's Rake tasks.