pretty sure hugo's mad about not providing a language to use for highlighting

content/posts/cooklang-server-and-systemd/index.md

@@ -22,7 +22,7 @@ Starting the cooklang server is very straightforward: `cook server`, or `cook se
 
 `systemd` uses [unit files](https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html) to configure resources it's responsible for. There's a lot going on in unit files so I've added as many comments as I could to explain what each lines does. Here, we're configuring a [service](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) which specifically describes a *process* that systemd is responsible for maintaining.
 
-{{< highlight >}}
+{{< highlight ini >}}
 [Unit]
 # Describe your unit. This is displayed in various system utilities for human administrators to understand what they're looking at.
 Description="cooklang web server"
@@ -54,7 +54,7 @@ WantedBy=multi-user.target
 {{< /highlight >}}
 
 With this unit file in place, my [recipes site](https://cook.ndumas.com) comes to life, with the help of a new block in my caddyfile:
-{{< highlight >}}
+{{< highlight ini >}}
 cook.ndumas.com {
     encode gzip
     reverse_proxy localhost:9080
@@ -66,7 +66,7 @@ Unfortunately, there's a catch. It looks like the cooklang server can't graceful
 The full solution involves creating two additional unit-files: `cooklang-watcher.service` and `cooklang-watcher.path`. As above, I'll annotate the (new) directives to explain their functionality.
 
 #### `cooklang-watcher.service`
-{{< highlight >}}
+{{< highlight ini >}}
 [Unit]
 Description=cooklang server restarter
 After=network.target
@@ -84,7 +84,7 @@ WantedBy=multi-user.target
 {{< /highlight >}}
 
 #### `cooklang-watcher.path`
-{{< highlight >}}
+{{< highlight ini >}}
 [Unit]
 Description="Monitor /home/cook/recipes for changes"