Blogging on The Lone C++ Coder's Blog

Static site migration - how I automated the static Hugo build and deployments for the blog

Timo Geusch — Sat, 13 Mar 2021 12:00:00 -0500

Good programmers are supposed to be lazy, right? The way I interpret this statement - because none of the software engineers who I know could be considered lazy - is that we like to automate repetitive tasks. You know, tasks like checking if you’ve made any changes to your blog and then building the blog and deploying the changes automatically. Which is what I’ve done, and in this post I’ll show you my minimalist setup to do so.

Static site migration - if you can read this, the blog has migrated to a static site

Timo Geusch — Fri, 12 Mar 2021 19:00:00 -0500

Right, if you and your RSS reader can read this, the first stage of the migration of my blog to a static site has successfully completed and you’re now reading the new site. There’s still some more tweaking to do, but I broke it up into multiple milestones to minimise the overall risk of the migration.

The next steps are mostly under the hood, where I clean up some of the oily bits and make sure things are running well and keep running that way. The main work remaining is migrating all content to a new web server, which is just one VM size bigger than the current one. The server is running FreeBSD and uses ZFS, and ZFS benefits a lot from having as much RAM available as I’m willing to pay for. Plus, I’m using this as an excuse to script up the (re-)creation of the server via Ansible so it at least moves from “pet” status to “livestock” status.

Static site migration - we have working comments with isso!

Timo Geusch — Mon, 15 Feb 2021 22:00:00 -0500

One “biggie” that was holding up this blog’s migration to a static site was getting a comments system up and running, followed by importing the existing comments. I had picked Isso a while back as it allows for easy import of existing comments from WordPress. I really didn’t want to depend on a third party comment hosting service like Disqus. I also didn’t want to use Staticman, mainly because it has dependencies on other services like Github or Gitlab. So Isso it was as that allows me to host everything on my own server.

Static site migration - starting the optimisation, already

Timo Geusch — Sun, 17 Jan 2021 22:30:00 -0500

Now that I’ve got the static site up and running, it’s obviously time to switch over immediately, right? Not to fast. After QA’ing my deployment process in production, it was time to check how the two compared from a performance perspective. I like to use several different tests, starting with Pingdom, then using PageSpeed Insights for more details.

The Pingdom speed test gave it a thumbs up, but they’re not running the currently dominant search engine. Fortunately said search engine also offers performance check tooling. This wasn’t quite the thumbs up I had hoped for, though. While the mobile performance is similar - in other words, equally unimpressive - the desktop performance is pretty good for both sites. The WordPress site still has a slight advantages, but after some initial tweaks like disabling highlight.js (the static site uses the basic Hugo highlighter), the static site is pretty close.

Postmortem of the unexpected blog outage

Timo Geusch — Tue, 25 Dec 2018 09:29:04 +0000

Straight from the “make work for yourself because there aren’t enough hours in the day already” files.

I’ve mentioned before that I am self-hosting this blog rather than using a hosted instance. I hosted the WordPress instance on FreeBSD and it’s been running quite well for a while, but during a double FreeBSD port upgrade to WordPress 5.0.1 and PHP 7.2 – after the php 7.0 port had been discontinued – broke the blog. php-fpm failed regularly with a signal 10, but I wasn’t able to figure out why in a hurry, so I started looking at alternatives.

Sorry for the disruption, normal service will resume shortly

Timo Geusch — Sat, 22 Dec 2018 21:00:00 +0000

My apologies for the sudden instability of my blog. I’ve managed to make a hash of an update on the main Wordpress site when trying to update to a newer PHP version and had to switch to the Jekyll “backup” site that isn’t quite production ready yet.

Comments will be available in due course, at the moment I’m trying to get the static site fully functioning and the various RSS feeds going again.

Digg Reader shuts down, and thoughts on organising my blog reading

Timo Geusch — Sun, 25 Mar 2018 13:00:33 +0000

Farewell, Digg Reader

Unfortunately, Digg announced that Digg Reader is shutting down tomorrow. While I never used Digg Reader as my main RSS feed reader – I’ve got a paid subscription to Feedly – I was very happy to use it as a backup reader for those feeds that weren’t always that great at adhering to the RSS feed standard (I’m looking at you, bringatrailer.com) as it was more forgiving when it parsed feeds. Unfortunately it appears to be another one of the “feed readers are dying” incidents that seems to have started when Google Reader was shut down. There weren’t really that many alternatives in the first place unless one wanted to self host.

Cleaning up UTF-8 character entities when exporting from WordPress to Jekyll

Timo Geusch — Sun, 27 Aug 2017 12:00:00 +0000

I’ve been experimenting with converting this blog to Jekyll or another static blog generator. I’m sticking with Jekyll at the moment due to its ease of use and its plugin environment. The main idea behind this is to reduce the resource consumption and hopefully also speed up the delivery of the blog. In fact, there is a static version of the blog available right now, even though it’s kinda pre-alpha and not always up to date. The Jekyll version also doesn’t have the comments set up yet nor does it have a theme I like, so it’s still very much work in slow progress.

To export the contents from WordPress to Jekyll I use the surprisingly named WordPress to Jekyll exporter plugin. This plugin dumps the whole WordPress data including pictures into a zip file in a format that is mostly markdown grokked by Jekyll. It doesn’t convert all the links to markdown, so the generated files need some manual cleanup. One problem I keep running into is that the exporter dumps out certain UTF-8 character entities as their numerical code. Unfortunately when processing the data with Jekyll afterwards, those UTF-8 entities get turned into strings that are displayed as is. Please note I’m not complaining about this functionality, I’d rather have this information preserved so I can rework it later on. So I wrote a script to help with this task.

The blogging hiatus is almost over

Timo Geusch — Fri, 20 May 2016 05:58:45 +0000

I switched jobs in October last year and getting up to speed in the new role did take priority over anything else, so I had to put a few other endeavours including this blog on hold for a little while.

The publishing frequency will still be lower than previously, but as I have moved from a mostly managerial role back to a pure software engineering role, I will be able to post more articles in line with the original intent of the blog, ie more C++-related articles and of course, the usual smattering of “look what cool feature I found in Emacs”.

Scheduling WordPress posts with org2blog

Timo Geusch — Mon, 10 Aug 2015 16:32:00 +0000

Another metablogging post, but this may come in handy for people who like to produce blog posts in bulk and schedule them for publication in WordPress at a later date.

In my case, my ability to find time to blog is directly correlated to my workload in my day job. That’s why you see regular gaps in my posting that may last for a few weeks to a month or two.

Improving my blogging workflow using Emacs (of course)

Timo Geusch — Mon, 02 Mar 2015 21:02:00 +0000

I try not to post too many metablogging posts. Other people do it better and I’m trying to focus on journalling what I learn as a software engineer and manager, not what tools I use for blogging. However after losing another post to WordPress’s built-in editor I decided Something Must Be Done. I think this is only the second post I lost, but it’s a fairly regular occurrence for a journalist friend of mine and I really don’t have that much time to retype blog entries that ended up in Bit Nirvana.

Of course I have to post something about Google Reader, too

Timo Geusch — Fri, 22 Mar 2013 07:05:24 +0000

The demise of Google reader viewed from a slightly different perspective. I find the analysis from someone who isn’t a proto-geek but rather an investment professional interesting, mainly because there are insights that some like me - who doesn’t spend the whole day looking at companies and trying to figure out what they are doing as opposed to what they say they are doing - would and this case, have missed.

Welcome back to the new blog, almost the same as the old blog

Timo Geusch — Tue, 13 Jul 2010 05:05:54 +0000

The move to the other side of the Atlantic from the UK is almost complete, I’m just waiting for my household items - and more importantly, my computer books etc - to turn up. So it’s time to start blogging again in the next few weeks. Due to some server trouble in the UK, combined with the fact that I do like Serendipity as a blogging system but was never 100% happy with it, I’ve switched to using WordPress on a server here in the US. The old blog will stay up, at least as long as the server stays put, but I won’t add any new content to the old blog.