One of the things that frustrated me about Kirby last year was handling code/template changes vs content changes. I complained about it here.
Ideally, since Kirby is a PHP CMS, I would do everything directly on the server. What I’ve done more often instead, is to run a full copy locally and rsync the final product (code, blueprints, content, images, etc.) to the production instance. Content is kept in plain text files, so both code and content changes need to be kept in sync.
We’re back on Hugo for baty.net.
For the past few months, I’ve been learning how to create a blog using Kirby CMS and it’s been a blast. Kirby is pleasant, easy, and fun to use. I’m glad I did it.
I won’t bother you with a 2,000-word rationalization piece about switching. I just felt like using Hugo again, so here we are.
I missed my nice Emacs-based publishing workflow. I missed “normal” YAML front matter. I missed having a completely static website. Who knows where we’ll be in a month, but today we’re using Hugo. I went back to the PaperMod theme. I don’t love how boring it is, but it’s clean, feature-rich, frequently updated, and easy to customize.
After yesterday’s Kirby->Hugo-Kirby debacle, I’ve been thinking about why I spend so much time farting around with and on my blog. Fair question, and one I don’t really have an answer to. I guess it’s my little place on the internet and I like to have the furniture arranged just so. But “just so” changes all the time, so I keep trying new configurations. It’s fun. Also useless, and nobody but me cares, but still.
Have you ever been so enamoured with plain-text-static-html publishing that you’re willing to burn down a month of implementing a blog using Kirby CMS in order to go back to using Emacs and Markdown and Hugo?
I have.
⚠️ This blog is no longer running Kirby, but I left this here just in case.
I’ve recently whittled my servers at DigitalOcean down to a single 2GB instance running Caddy. When I started playing with Kirby, I tried getting it running there, but had issues with php-fpm and Caddy not playing well together, so I spun up a hosted instance at (link: https://fortrabbit.com/ text: Fortrabbit).
Running Kirby doesn’t require a database or anything fancy, just a web server and PHP, and it bugged me that I couldn’t get it working, so yesterday I tried again, and finally figured it out. I’m writing this down so that I don’t lose it.