I have been playing with the idea of leaving Wordpress behind as the content publishing platform for my Alien Pastures blog.
Wordpress is great software and it's versatile and offers a wealth of plugins that allow the blog owner to do all kinds of nice stuff. For me it was the ideal solution at the time when I wanted to create a blog and was looking for something self-hosted but also self-contained (the whole blog in one single directory). I was not sure if I would be able to keep running it on the server where the blog was born, therefore something like Wordpress CMS combined with a SQLite file-based database backend was perfect.
That was 16 years ago, and the blog moved servers, grew a lot in content and it uses a proper MariaDB backend now. But it puts a strain on the servers where I host(ed) it; the stable Slackware versions (first 14.2, then 15.0) have become stale and Wordpress started requiring versions of PHP and MariaDB that were not available for the Slackware version I was using... also the blog increasingly needs protection from scammers, spammers, AI-bot-scrapers and hackers; it needs performance tweaks to deal with server load and executing the interpreted PHP code in which Wordpress is written, and there are security vulnerabilities discovered in Wordpress and its plugins all the time.
When today I had to upgrade the Wordpress code and a good ten plugins again because of a un-authenticated Remote Code Execution (RCE) vulnerability, accompanied by stern warnings to "backup your database first!", I knew that my research would ultimately pay off.
I decided to move forward with an experiment I have been conducting for a while. My future blog pages will all be static HTML. Nothing is interpreted, nothing is vulnerable other than potentially Apache or Slackware itself, and I will use a Docker container for a part of the new setup.
That setup is based on a new (private) git repository which will hold my blog's content after it has been converted from Wordpress syntax into Hugo syntax and layout. Hugo is a static site generator, written in Go. How that will work with this git repository?
- I run a converter on a full export of the Wordpress blog (that's a single XML file containing everything except the media files) to generate a collection of static HTML pages that will become the "legacy" part of the new blog.
- In a private repository on the Slackware Forge I will store the Hugo framework defining the layout of my blog, the theme for my blog (a Hugo port of the GPL-licensed Wordpress theme 'Hemingway' by Anders Norén which I currently use), the converted legacy (Wordpress) content plus the Sveltia in-browser editor which I will be using to write and publish new articles. Sveltia can read the repository's full content and can also write to that repository.
- Since a Hugo-generated static web site does not know the concept of a comments section because that goes against the static page concept, I will run a self-hosted Artalk comments server in Docker. My new blog will load the comments below each blog article by asking the Artalk server for them over a trusted connection, protected by Docker secrets.
- When someone posts a comment, it is held in a moderation queue, unless that someone (the combination of nickname and email address) already has an earlier approved comment, in which case the comment will automatically be approved by a moderator bot within the minute. This moderation plugs into an Akismet anti-spam service just like I have right now on the Wordpress blog. It will prevent me from having to deal with a hundred spam comments per day.
- When I make a change to the repository (updating the blog layout, adding a new theme, whatever) this triggers a Forgejo CI workflow in git. Those triggers are very similar to Github runners if you use CI on Github (or any other git platform). The Forgejo runner starts a Docker image which contains Hugo; Hugo fetches the repository content, renders the lot into static HTML pages and packs the whole set into a registry package.
- A cron job on the blog server polls the Forge for updated site content packages every two minutes, and pulls that package when one becomes available. It unpacks the tarball (it's nothing more than that), checks if the sha256 checksum is correct and then refreshes the blog's content - the pages which you are seeing.
- When I want to write or update an article, I launch Sveltia (via a hidden URL on the blog), login to the Slackware Forge and start writing. When I click "publish", Sveltia will commit my article to the private repository, triggering the CI workflow, and two minutes later the new article is online.
When I save an article in Draft, then Sveltia commits the article in a temporary git branch; any branch except "main" will never trigger the CI workflow, so you will never see my drafts by accident :-)
There's a lot of moving parts in that setup, and it is not as straight-forward as Wordpress; but it is a good learning experience into Git workflows. Also, the constituent parts (except for the free tier of the online Akismet anti-spam service) that I deploy locally are not tied to any kind of commercial entity and fully open source. And it's a hundred percent safe solution.
And... you may have noticed that I wrote the above plan in great detail. That is because I have all of this already running as a staging server while I debug this new setup, remove the kinks and tweak everything to my liking. Feel free to look and click around, post comments if you want, but know that all of that will be wiped again when I make the switch. Also the content of that staging server is frozen to the moment when I did the last content conversion. This new post will not appear there.
Have a look at https://hugo.slackware.nl/ and tell me when you find bugs. I need some time for an actual cut-over and I am not yet completely happy with the Sveltia editor setup, so Wordpress will remain the blog's CMS for a while.
The hugo-builder repository on the Slackware Forge on the other hand, is open to anyone who is curious to start experimenting with Hugo themselves; it contains the code that generates the Docker image used by the aforementioned CI workflow.
I added a subdirectory 'workflow-example' which contains a copy of the actual CI runner that I am using for the new Alien Pastures blog. You can copy that into your own repository and rename the directory to '.forgejo'; you'd also have to do some small modifications and define some variables and secrets in your Forge account to make it work for your own future Hugo website.

Comments