Add a "containers" tag

content/posts/containers-as-root.md

@@ -2,7 +2,7 @@
 title: Container processes shouldn't run as root!
 subtitle: \"What's wrong with containers running as root?\"
 date: 2020-08-18
-tags: [self-hosting, security]
+tags: [self-hosting, security, containers]
 image: https://www.threatstack.com/wp-content/uploads/2017/06/docker-cloud-twitter-card.png
 ---
 

content/posts/goaccess-analytics.md

@@ -1,7 +1,7 @@
 ---
 title: Privacy-respecting analytics with GoAccess
 date: 2020-04-10
-tags: [self-hosting]
+tags: [self-hosting, containers]
 ---
 
 Recently, I decided to put some analytics on my website. Would be nice to see what view number are like and what pages get the most traffic.

content/posts/keeping-docker-containers-updated.md

@@ -2,7 +2,7 @@
 title: Keeping your Docker containers up to date
 subtitle: Updating your applications with minimal effort
 date: 2020-07-27
-tags: [self-hosting]
+tags: [self-hosting, containers]
 ---
 
 Last year, I switched all of my hosting from arbitrarily installed packages to Docker. This made installing and configuring incredibly simple, but updating a little less defined. Whilst Docker itself is updated through the system package manager (probably), the containers themselves aren't.

content/posts/self-hosting-plausible/index.md

@@ -3,7 +3,7 @@ title: Self hosting Plausible
 date: 2020-08-05
 image: resource:plausible-login.png
 subtitle: Simple and privacy-friendly alternative to Google Analytics
-tags: [self-hosting]
+tags: [self-hosting, containers]
 ---
 
 I only recently talked about using [GoAccess]({{< relref "goaccess-analytics" >}}) as an analytics tool. Over the last couple months, I've been more interested in how many hits this website actually gets. GoAccess was a really simple solution which worked on log files and only captured the bits of information I really cared about: Page views.

content/posts/self-hosting-website/index.md

@@ -1,7 +1,7 @@
 ---
 title: Self hosting my website
 date: 2020-04-11
-tags: [self-hosting]
+tags: [self-hosting, containers]
 ---
 
 A few days ago, I was sharing a [blog post]({{< relref "wireguard-haproxy-gateway" >}}) to someone on the [self-hosted podcast](https://selfhosted.show/) discord, and they asked if I was self hosting my website. Unfortunately, and rather ironically, I had to answer no. I've been intending to move it over to my own server for a while, so this felt like as good of a push as any!

content/posts/traefik-basics/index.md

@@ -2,7 +2,7 @@
 title: Traefik Basics
 date: 2020-05-01
 image: https://docs.traefik.io/assets/img/traefik-architecture.png
-tags: [self-hosting]
+tags: [self-hosting, containers]
 ---
 
 [Traefik](https://docs.traefik.io/) is a cloud native reverse proxy, which is basically a fancy way of saying it's a reverse proxy with some fancy features. Specifically it has fancy features around auto-discovery, and deep integration with technologies like Docker and Kubernetes.

content/tags/containers/_index.md

@@ -0,0 +1,5 @@
+---
+title: Containers
+---
+
+Not all containers are [whales :whale:](https://www.docker.com/).