grop.dev

This Blog Is Now Haunted 👻

2026-10-03T13:23:00Z

And perfect timing for October! 🎃

Since I've started this blog I've been more and more intrigued by GNU Guix, Guile Scheme and LISP dialects in general. It then seemed only fitting that when I found the awesome looking project, Haunt, I had to try it out.

Haunt is a static website generator, just like Hugo (that I used previously), but written entirely in Guile Scheme. You define your entire website just as you would a scheme program. For example, this blog is defined (partly) like this:

(use-modules (haunt asset)
             (haunt builder blog)
             (haunt builder atom)
             (haunt builder assets)
             (haunt builder flat-pages)
             (haunt builder redirects)
             (haunt reader commonmark)
             (haunt post)
             (haunt site)
             (grop.dev theme)
             ((grop.dev redirects) #:prefix grop:)
             (grop.dev commonmark))

(define post-prefix "/posts")

(define collections
  `(("Posts" "posts.html" ,posts/reverse-chronological)))

(site #:title "grop.dev"
      #:domain "grop.dev"
      #:default-metadata
      '((author . "Gunnar Grop")
        (email  . "gunnar.grop@protonmail.com"))
      #:readers (list commonmark-reader*)
      #:builders (list (blog #:theme grop-theme
                             #:collections collections
                             #:post-prefix post-prefix)
                       (redirects grop:redirects)
                       (atom-feed #:blog-prefix post-prefix
                                  #:file-name "posts/index.xml")
                       (atom-feeds-by-tag #:blog-prefix post-prefix)
                       (flat-pages "pages"
                                   #:template flat-page-template)
                       (static-directory "css")
                       (static-directory "assets/images")
                       (static-directory "assets/text")))

Thus far I really like it. It's much harder to get started with, compared to Hugo, if you don't already have experience with Guile Scheme. But, at the same time it's much simpler. I also really like that you can define HTML (really XML) with S-expressions using SXML.

Unfortunately I've had to sacrifice some things, like a nice Tags page, and syntax highlighting for YAML snippets. But I'm sure I'll even out these drawbacks in the near future. I'm here mostly to learn scheme anyway.

So, for the foreseeable future I'll keep using Haunt. I recommend you do to, if you're looking for a simple but very cool static website generator.

Big thanks to David Thompson for creating Haunt.

New Hugo Theme

2026-08-23T22:47:00Z

Just a PSA. I've been building this website with Hugo since the beginning, and ever since then I've used the theme poison. It's a good theme, but I just grew bored of it. I wanted something a bit cleaner, that didn't have as much "wasted" whitespace.

So I replaced it with noJS. Thus far I'm happy with it. It seems easier to navigate than my previous theme, so I think I'll be using this for the unforeseeable future. 🙂

Full RSS Feed

2026-05-14T15:57:00Z

When I started this blog I didn't know that Hugo just shows the summary of each post in the default posts RSS feed.

That has now been corrected, so if you subscribe to my RSS feed you now see the full posts in your RSS client.

Thank you to Junian for their post "Full-Text RSS in Hugo" that showed me how to do this. Please read their blog post if you're looking to do this for your own blog.

Publishing Static Sites on sourcehut pages

2025-10-22T10:16:00Z

Abstract

I mentioned in a previous post that I use Kubernetes to deploy my blog. Since my professional work (and my homelab) consists primarily of managing Kubernetes deployments, this didn't seem like a bad idea. Albeit a bit overkill. But I had all the infrastructure in place, so I went with it.

I've also mentioned that I've migrated all my personal git repositories over to sourcehut recently, but it wasn't until yesterday that my brain registered that sourcehut has another component, pages, that allow you to publish static websites... This is way easier!

Not only is it super easy to use, and integrates well with other sourcehut components (git/hg, builds), but every user even gets their own domain, in the form of username.srht.site. It's also very easy to use your own custom domains! This can be done at your domain registrar, by pointing you DNS records to the following IPv4 (A record) and IPv6 (AAAA record) addresses.

@ IN A 46.23.81.157
@ IN AAAA 2a03:6000:1813:1337::157

Note: These IP addresses might be subject to changes. Please always refer to the official documentation.

Anyhow, I thought I might do a little write-up on how to use sourcehut pages, and just to tell you that I've migrated this blog over to it.

Publishing your Site

You'll only need a few things for this to work.

A sourcehut account.
A sourcehut git repository containing you static site (I'm using Hugo).
A sourcehut build manifest to publish your site.

You can take a log at the source code for this blog, if you want a reference on what such a git repo might look like: https://git.sr.ht/~gunnargrop/grop.dev.

The name of the git repository should preferably be the name of the site. In my case, the repo is called "grop.dev". In your case it might be called "username.srht.site".

After you have your git repository, we just have to create a build manifest. This is done by creating a file called .build in the root of the repository. The file will look something like this:

---
image: alpine/latest

oauth: pages.sr.ht/PAGES:RW

packages:
  - hut
  - hugo

environment:
  site: username.srht.site

tasks:
  - package: |
      cd $site
      hugo
      tar -C public -cvz . > ../site.tar.gz

  - upload: |
      hut pages publish -d $site site.tar.gz

And that's it! After you've created this build manifest, whenever you push changes a commit to your repository, this build manifest will trigger and publish your Hugo site to your sourcehut page. Which you can then visit at https://username.srht.site. 🙂

Of note here is that we're using a tool called hut, a CLI tool to interact with sourcehut. It authenticates to sourcehut using OAuth2 token, which the build system has a handy keyword for. The oauth keyword takes care of generating a token for us, that the CLI tool will use in our build.

# In this case, we generate a token that grants us read/write
# permissions to the sourcehut pages API
oauth: pages.sr.ht/PAGES:RW

But is this CI good enough? I don't think so, since I don't want changes to get published every time I push something to my repo. This can be solved by just not triggering the CI when we push something, like so:

git push --push-option skip-ci

That's what I do normally, to not unnecessarily waste sourcehut resources, but I also added another part to the build manifest, so it just publishes my page when I push a new git tag to the repo.

---
image: alpine/latest

oauth: pages.sr.ht/PAGES:RW

packages:
  - hut
  - hugo

environment:
  site: grop.dev

tasks:
  - setup: |
      # Exit pipeline if NOT triggered by tag
      if [[ "$GIT_REF" != refs/tags/* ]]; then
          complete-build
      fi

  - package: |
      cd $site
      hugo
      tar -C public -cvz . > ../site.tar.gz

  - upload: |
      hut pages publish -d $site site.tar.gz

Conclusion

As you can see, it's in fact very easy to publish your own static site to sourcehut pages. I would recommend giving it a go if you want an easy place to host you blog, or whatever else!

Introductions

2025-09-16T17:29:00Z

My first blog post!

Greetings to everyone and anyone who might be reading this. My name is Gunnar Andersson, also known as my internet nickname, GunnarGrop.

I guess I'm just a typical nerd with an interest in Linux, Emacs and Kubernetes. But if you want to know more about me you can just read my home page.

The reason I wanted to start this blog is because I often stumble upon, to me, interesting facts and solutions to Linux or Kubernetes problems that I've wished I'd write down somewhere. So not only is the purpose of this blog to share my thoughts and finding with other people, but also just to share my thought with my future self.

Another reason I wanted to start this blog is simply because I thought it would be fun. I've seen this static website generator being mentioned everywhere online, Hugo (which I'm using to generate this blog), and I wanted to try it out. Not only that, but I also wanted to try out a popular Emacs package, ox-hugo. This is of course my first blog post, but being able to write posts at all in org-mode is just so cool!

I've experimented a little bit with my setup before taking this blog online, so I've also tried the easy-hugo Emacs package. But, to be honest, I think I like ox-hugo way more. Easy-hugo seems like a good project, but it assumes that you'll be writing Hugo files in Markdown, which is of course fully reasonable (it is the native langauge of Hugo, after all), but it feels like a wasted opportunity to not write in org-mode, when you're already using Emacs.

Anyway, I'll try this out for a while and see how I like it. If you're interested in the stuff I post about, please consider subscribing to my RSS feed or throw me an e-mail! You can find my contact information in the left sidebar. 🙂