From WordPress to Hugo
-
Julia Evans ☛ Some notes on upgrading Hugo
Warning: this is a post about very boring yakshaving, probably only of interest to people who are trying to upgrade Hugo from a very old version to a new version. But what are blogs for if not documenting one’s very boring yakshaves from time to time?
So yesterday I decided to try to upgrade Hugo. There’s no real reason to do this – I’ve been using Hugo version 0.40 to generate this blog since 2018, it works fine, and I don’t have any problems with it. But I thought – maybe it won’t be as hard as I think, and I kind of like a tedious computer task sometimes!
-
Lee Peterson ☛ It’s time to stop paying WordPress
I’ve got a lot on, I’m feeling overwhelmed but I can’t keep paying WordPress for its services with the current CEO at the helm.
-
[Old] Ashish Bhatia ☛ Migrating from WordPress to Hugo
The stack I eventually ended up with is
1. Markdown - all posts have to be in Markdown. Overtime, I have fallen in love with writing posts in Markdown and have been copying it over to WordPress.
2. Single container deployment - Deployment as a single container on Google Cloud Run
3. Hugo - Tooling written in interpreted languages like Python and TypeScript decays really quickly over time. The fact that Hugo was written in Go was a huge upsell for me. I, myself, have written several tools and have always felt that the code maintainability of languages like Go is much higher than Python.
4. Busybox - To minimize the attack surface even further, my final docker image contains HTML, CSS, Javascript, and only one binary busybox-httpd server. I don’t think one can cut the attack surface more than this.