I knew I couldn’t stay away from the automation bug for much longer. So I spent a good day or so familiarising myself with Hugo’s Templating and how Data Templates work. With a bit of trial error and a lot of squinting at syntax errors, I’ve managed to come up with a fairly good system.
Firstly, I extended the syntax in the params section of the config.yaml. You can now eschew the max and now keys and instead provide a file:
Earlier this year, I started to track progress for my painting challenge. It’s been going well and I’ve a lot of fun tracking the numbers and seeing them go up. One thing I was keen on though, was to improve the update process. Updating the markdown page for the challenge and calculating the percentage progress by hand, is hardly difficult or time-consuming, but anyone who’s read my blog will know that I like automating things.
When I started writing this blog, I had put aside a spare Raspberry Pi as kind of “dev” server. A place I could freely install stuff, test out code and run my Ansible playbooks. The main reason to keep this separate from the server which runs all my services was because there was limited disk space on the server1.
One of the biggest challenges was to keep my version of hugo up-to-date and to remember not to publish my blog entries with the draft switch enabled2.
The most annoying thing about having a website or blog for me has always been in writing content for it. Getting stuff published is a close second though. So when I wanted to revive this blog and actually have a proper web presence for once, I resolved that it should be as easy as possible to do it.
So first thing I did was to put this blog up as a Github repo so that I could access it from anywhere.