Add makefile with release steps.

Makefile

@@ -0,0 +1,7 @@
+.PHONY: render
+
+render:
+	quarto render
+
+sync:
+	rsync -a _site/. packaging@vpn.jpace121.net:/var/www/til.jpace121.net/.

_drafts/self_hosted_git_summary.qmd

@@ -16,4 +16,34 @@ Options:
 2. gitlab
 3. onedev
 4. gerrit
+
+gitea:
+1. Lightweight
+2. Easy to host, just add a docker container.
+3. Not the most mature open source community based on their
+   github PRs.
+4. They host their development on github...
+5. Heavy development in China, which is not great for US Defense
+   oriented companies
+
+gitlab:
+1. Most feature complete, with really good integrations with all kinds of stuff.
+2. Almost every thing I've seen integrates with gitlab.
+3. Fat. Hosted on a VM with 4Gb of RAM, the server kept getting OOM killed when I
+   was just logged into the admin panel. I currently host all my infrastrture
+   apps in a single VM with 4Gb of ram.
+
+Onedev:
+1. Has lots of features.
+2. LIghtweight
+3. Only a single developer doing most of the development, no real open source community.
+4. Lots of little bugs that added up.
+
+gerrit:
+1. Had the bet review process
+2. Really easy to write custom integrations with.
+3. Felt "powerful" using it.
+4. Code display interface sucks.
+5. Workflow very different than github.
+
 -->

index.qmd

@@ -2,8 +2,8 @@
 title: "Welcome!"
 toc: false
 listing:
-   id: blog-listing
-   contents: blog
+   id: post-listing
+   contents: posts
    type: table
    fields: [title, date]
    sort: "date desc"
@@ -20,5 +20,5 @@ today isn't nearly as interesting.
 
 ## Latest Posts
 
-::: {#blog-listing}
+::: {#post-listing}
 :::

posts.qmd

@@ -2,7 +2,7 @@
 title: "Posts"
 toc: false
 listing:
-   contents: blog
+   contents: posts
    type: table
    fields: [title, date]
    sort: "date desc"

posts/yocto_best_tutorial.qmd

@@ -0,0 +1,23 @@
+---
+title: "Best Yocto Tutorial"
+author: "James Pace"
+date: "2024/01/26"
+---
+
+The [Yocto Project](https://www.yoctoproject.org/) is a project that develops
+a set of tools for building a custom embedded Linux distribution.
+
+Yocto can be overly complex, and the official documentation, while complete,
+does not provide a great on ramp.
+It's pretty easy to do the "first step" sort of stuff, but the learning curve
+after that is sort of a cliff.
+
+The best documentation I've found for learning Yocto (which I'm currently working through)
+is the slides and labs from Bootlin's Yocto Training, which can be found online for free
+[here](https://bootlin.com/training/yocto/).
+
+After reading through the slides, I had a lot more clarity when looking at other examples
+I found online.
+
+I'm still working through the labs, and will post things I learn on this site as
+I learn them.