add a thing-a-month meta project

content/micro/thing-a-month-02-02.md

@@ -2,6 +2,9 @@
 title = "shopping for a scheduler"
 description = "evaluating tradeoffs between Kubernetes and Nomad"
 date = 2024-02-07
+
+[extra]
+project = "thing-a-month (meta)"
 +++
 
 The first thing on my "meta" list is to get my house in order with how I deploy things. Right now I have a single VM in DigitalOcean that runs my blog, git.bytes.zone, and a couple other smaller static sites. (See [clown computing](@/posts/clown-computing.md).)

content/micro/thing-a-month-02-03.md

@@ -1,6 +1,9 @@
 +++
 title = "a Kubernetes shopping list"
 date = 2024-02-08T06:12:53-06:00
+
+[extra]
+project = "thing-a-month (meta)"
 +++
 
 I talked to a few people yesterday—it sounds like Kubernetes is where it's at. I really enjoyed Nomad back in the day, but it looks like I'd have to do a lot of roll-your-own, which kind of negates the benefit of operational simplicity for me.

content/projects/thing-a-month-meta.md

@@ -0,0 +1,12 @@
++++
+title = "thing-a-month (meta)"
+description = "setting the stage for the rest of the project"
+date = 2024-02-06T00:00:00-06:00
+
+[extra]
+when = "now"
++++
+
+The first project in [thing-a-month](@/projects/thing-a-month.md) will be laying the foundation for the rest of the work. (Here's [the intro post where I talk about this](@/micro/thing-a-month-02-01.md).)
+
+I've been running my own infrastructure for a while now but it's gotten really messy recently. Instead of throwing more stuff into that, I'm going to try and get things set up in a less chaotic way. This might seem like overkill, but I see benefits I could get immediately!

content/projects/thing-a-month.md

@@ -1,7 +1,7 @@
 +++
 title = "thing-a-month"
 description = "making cool stuff in a time-constrained way"
-date = 2024-02-06
+date = 2024-02-06T12:00:00-06:00
 
 [extra]
 when = "now"