Michael Blum

Developer from Chicago

Hugo Now: Porting A Theme To Hugo July 3, 2017

Create a Theme Simple as hugo new theme [name]. Documentation can be found here: Hugo Themes Hugo, due to it being only a few years old, has fewer themes compared to Jekyll Luckily, it’s expected that you will want to port a theme to Hugo. I decided to port this blog’s theme: Jekyll Now, to Hugo. Jekyll Now A very popular theme jekyll-now (3,701 , 15,076 ), I wanted to retain the spirit of Jekyll Now while updating it’s dependencies as the last commit was over a year ago.

Migrating From Jekyll To Hugo July 3, 2017

Migrating from Jekyll Why go to the trouble? While Jekyll has been good to me and shown me the light of static blogging, Jekyll’s unabashed Ruby / Ruby on Rails underpinnings lead to some interesting problems: 1. Ruby version / Ruby env problems Recently update your operating system? Via brew pr another tool? Chances are your Ruby environment will complain. Since I’m not a ruby person by trade, I haven’t devoted the time to running ruby well.

Building a Blog Part 4 - Deploying to Amazon S3 April 17, 2016

Going Live After Building a Blog Part 3 - Continuous Integration with Gitlab CI - its time to automate deploying our blog to a host. Amazon’s Simple Storage Service (S3) is a good choice for serving static assets on the cheap. S3 is a bit different from a traditional VPC like DigitalOcean or Amazon’s Elastic Compute Cloud (EC2). Pros Very cheap - With AWS you pay as you go. Rather then paying $5-10 a month running a server for our static site, we can store our site for fractions of a penny:

Building a Blog Part 1 - Docker + Jekyll April 9, 2016

Welcome to the inaugural post of mblum.me. I figured a good start to this blog would be a series of posts on how this blog can to be: from development to production. Why use Docker? A valid question. Looking at the Jekyll Quick Start it should be as simple as: gem install jekyll && jekyll serve What I found to be difficult as when more gems came into play or my version of Ruby on my host machine was wrong (my Linux workstation has an old Ruby install).