Hugo, Tailwind & Netlify = <3

So one of the major things that I have an issue with is getting simple websites/projects up and running. Luckily we live in the future. There are services for all sorts of things and many of them are free, open source or extremely low cost. At the end of the day, the only thing holding people back is time. Why Hugo/Tailwind/Netlify Hugo Hugo is a great framework for creating websites from markdown files.

Logitech Harmony 650 Hardware Overview

Recently, I have been interested in seeing how the Logitech Harmony 650 remote looks like from a hardware standpoint, primarily since the software to program the devices is absolutely horrible to work with. My primary gripe with it is that its a wrapper around a webpage and very difficult to do certain tasks and has very specific opinions on how your entertainment center is setup. There has been some work in a project called concordance, but I’m not sure that it will fit my needs and still relies on interacting with the logitech site to get codes for the remote and basically just acts like a command line interface for pushing configs to the remote.

Github Actions Hugo Deploy

GitHub Actions GitHub actions is a really simple way of executing code in the context of a GitHub repository. For example building images, testing or deployment in a very minimal way using docker images. It is currently in beta, so its very likely that things might have changed by the time you read this. Automatic Hugo deployment on GitHub pages There are a couple ways of automatically deploying hugo sites, but actions are a great way to automatically build/push websites.

Converting to Hugo

For a while I have been using Pelican, which for most of my needs has worked extremely well. However, recently I came across a new static content generator called Hugo. One of the first things that I noticed with hugo was how many of the patterns that it uses just kind of “click” and I figured I should give it a run. There are quite a few advantages to using a static site generator vs a traditional CMS:

Using ansible to provision local certificates using letsencrypt

Over the weekend, I ran into a bit of a non-standard use case for LetsEncrypt(LE). Basically I have some vmware esxi and other boxes that aren’t capable of running letsencrypt certbotm but I wanted to give them valid certificates. Certbot is awesome and definitely the easiest way to get LE up and running for 99% of the folks out there. However, the most common way certbot validates domains/hostnames is by using the http validation and using its own directory.

Pelican Navbar by Page

Authors note: since this post was written, quite a few things have changed. I still vastly prefer static content generation, but have since switched to Hugo. While it may not be obvious, this site is entirely generated by pelican. This gives a couple nice benefits: Simplicity, Security and a good deal of Customization. Additionally since it uses Jinja templates, it is something that I am very familiar and comfortable with. Additionally, the blog posts are written in Markdown, which means that between the two things, it is fairly robust and straightforward.