6 files changed, 36 insertions, 24 deletions
diff --git a/content/blog/1password-ssh-agent.md b/content/blog/1password-ssh-agent.md
index 0561137..5d5d436 100644
--- a/content/blog/1password-ssh-agent.md
+++ b/content/blog/1password-ssh-agent.md
@@ -1,7 +1,9 @@
----
-title: 1password's ssh agent and nix
-date: 2023-12-02
----
++++
+title = "1password's ssh agent and nix"
+date = 2023-12-02
+[taxonomies]
+tags = ["nix"]
++++
 
 [A while ago](https://blog.1password.com/1password-ssh-agent/), 1password introduced an SSH agent, and I've been using it for a while now. The following describe how I've configured it with `nix`. All my ssh keys are in 1password, and it's the only ssh agent I'm using at this point.
 
diff --git a/content/blog/git-link-and-sourcegraph.md b/content/blog/git-link-and-sourcegraph.md
index 073068d..c86b465 100644
--- a/content/blog/git-link-and-sourcegraph.md
+++ b/content/blog/git-link-and-sourcegraph.md
@@ -1,7 +1,9 @@
----
-title: emacs' git-link and sourcegraph
-date: 2021-08-24
----
++++
+title = "emacs' git-link and sourcegraph"
+date = 2021-08-24
+[taxonomies]
+tags = ["emacs"]
++++
 
 I use [sourcegraph](https://sourcegraph.com/) for searching code, and I sometimes need to share a link to the source code I'm looking at in a buffer. For this, the package [`git-link`](https://github.com/sshaw/git-link) is great.
 
diff --git a/content/blog/google-doc-failure.md b/content/blog/google-doc-failure.md
index ee98f9b..b4a65b9 100644
--- a/content/blog/google-doc-failure.md
+++ b/content/blog/google-doc-failure.md
@@ -1,7 +1,9 @@
----
-title: Google Doc Failures
-date: 2021-04-11
----
++++
+title = "Google Doc Failures"
+date = 2021-04-11
+[taxonomies]
+tags = ["practices"]
++++
 
 In most use cases, Google Doc is an effective tool to create "write once, read never" documents.
 
diff --git a/content/blog/leaving-twitter.md b/content/blog/leaving-twitter.md
index cb8e5c8..f7d98f5 100644
--- a/content/blog/leaving-twitter.md
+++ b/content/blog/leaving-twitter.md
@@ -1,7 +1,9 @@
----
-title: Leaving Twitter
-date: 2022-01-15
----
++++
+title = "Leaving Twitter"
+date = 2022-01-15
+[taxonomies]
+tags = ["work"]
++++
 
 January 7th 2022 was my last day at Twitter, after more than 7 years at the company.
 
diff --git a/content/blog/nix-raid-systemd-boot.md b/content/blog/nix-raid-systemd-boot.md
index cd020f2..de68695 100644
--- a/content/blog/nix-raid-systemd-boot.md
+++ b/content/blog/nix-raid-systemd-boot.md
@@ -1,7 +1,9 @@
----
-title: Workaround md raid boot issue in NixOS 22.11
-date: 2023-01-10
----
++++
+title = "Workaround md raid boot issue in NixOS 22.11"
+date = 2023-01-10
+[taxonomies]
+tags = ["nix"]
++++
 
 For about a year now I've been running [NixOS](https://nixos.org/ "NixOS") on my personal machines. Yesterday I decided to go ahead and upgrade my NAS from NixOS 22.05 to [22.11](https://nixos.org/blog/announcements.html#nixos-22.11). On that machine, all the disks are encrypted, and there are two RAID0 devices. To unlock the drives, I log into the [SSH daemon running in `initrd`](https://nixos.wiki/wiki/Remote_LUKS_Unlocking), where I can type my passphrase. This time however, instead of a prompt to unlock the disk, I see the following message:
 
diff --git a/content/blog/tailscale-docker-https.md b/content/blog/tailscale-docker-https.md
index 5a40809..1094ca6 100644
--- a/content/blog/tailscale-docker-https.md
+++ b/content/blog/tailscale-docker-https.md
@@ -1,7 +1,9 @@
----
-title: Tailscale, Docker and HTTPS
-date: 2021-12-29
----
++++
+title = "Tailscale, Docker and HTTPS"
+date = "2021-12-29"
+[taxonomies]
+tags = ["containers"]
++++
 
 I run a number of services in my home network. For the majority of these services, I don't want to make them available on the internet, I want to only be able to access them when I'm on my home network. However, sometimes I'm not at home and I still want to access them. So far I've been using plain [wireguard](https://www.wireguard.com/) to achieve this. While the initial configuration for wireguard is pretty simple, it starts to be a bit more cumbersome as I add more hosts/containers. It's also not easy to share keys with other folks if I want to give access to some of the machines or services. For that reason I decided to give a look at [tailscale](https://tailscale.com/).