<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Chrizzle23.net</title><link>https://chrizzle23.net/tags/git/</link><description>Recent content in Git on Chrizzle23.net</description><generator>Hugo</generator><language>en</language><copyright>Chrizzle23.net and all blog posts © 2026 by Chris Anderson is licensed under CC BY-NC-SA 4.0</copyright><lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chrizzle23.net/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up my writing environment</title><link>https://chrizzle23.net/posts/260911-workstation-setup/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/260911-workstation-setup/</guid><description>&lt;h1 id="setting-up-my-writing-environment">Setting up my writing environment&lt;/h1>
&lt;p>A major project that I took on over the summer was fixing my rather flat home network to include separate VLANs for me, the family, the various smart devices around the house, the DMZ, and my server network. During that project I thought, &amp;ldquo;how can I make this harder on myself?&amp;rdquo;&lt;/p>
&lt;p>I am not a particularly smart individual, so I like to keep things simple, so I assign a class C subnet to each VLAN, and I use numbers that I can easily remember:&lt;/p></description></item><item><title>Git Hooks pt2</title><link>https://chrizzle23.net/posts/250611-shell-script-from-hell-2/</link><pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/250611-shell-script-from-hell-2/</guid><description>&lt;h1 id="the-meat-grinder">The Meat Grinder&lt;/h1>
&lt;p>Git makes it possible for me to only have to worry about my MarkDown files. Or, someday I will only have to worry about MarkDown files. &lt;em>But it is not this day&lt;/em>.&lt;/p>
&lt;p>Hugo templates are fussy tools. They&amp;rsquo;re awesome when I can get them work, but getting to that point is maddening. And Git might as well be black magic for how well I understand it. Once I push my MD files up to the remote repo, the git hook calls &amp;lsquo;stage.sh&amp;rsquo; and &lt;em>IT&amp;rsquo;S SAUSAGIN TIME!&lt;/em>. The following is my cobbled together shell script to eat MD and vomit up websites. I should probably use python or something, but I am too jacked up on Mountain Dew to take on &lt;em>another growth opportunity&lt;/em>.&lt;/p></description></item><item><title>Git Hooks pt3</title><link>https://chrizzle23.net/posts/250611-shell-script-from-hell-3/</link><pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/250611-shell-script-from-hell-3/</guid><description>&lt;h1 id="actual-deployment">Actual Deployment&lt;/h1>
&lt;p>This whole &amp;ldquo;development pipeline&amp;rdquo; is a massive clunk. A collection of clunks, working together. &lt;em>Clunkware&lt;/em>. I haven&amp;rsquo;t attached this deployment script to a git hook. I want a chance to look at the staging site before I push it to production. &amp;ldquo;Production&amp;rdquo; for me is when the files are updated on The VPS. Pushing a non-working site to production is, as the Irish would say, &lt;em>not the best&lt;/em>. So I run the deployment script manually, which I will detail at the end of the post.&lt;/p></description></item><item><title>The Shell Script From Hell</title><link>https://chrizzle23.net/posts/250611-shell-script-from-hell-1/</link><pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/250611-shell-script-from-hell-1/</guid><description>&lt;h1 id="its-taken-me-60-hours-to-save-2-minutes-of-typing">IT&amp;rsquo;S TAKEN ME 60 HOURS TO SAVE 2 MINUTES OF TYPING&lt;/h1>
&lt;p>&lt;a href="https://git-scm.com/docs/githooks">Git hooks&lt;/a> are scripts of some kind that run when you do something in Git. Real developers (not me) use them to kick off a bunch of crap like QA tests, validation tools, sending messages to people, pretty much anything you can imagine. They do all kinds of things, but I am going to do the thing that I always do and barely scratch the surface of its potential. AND I am using it to run Bash scripts. If you are a proper dev, or DevOps type, this is your opportunity to look away.&lt;/p></description></item><item><title>Gitting back to Git</title><link>https://chrizzle23.net/posts/250610-git-stuff/</link><pubDate>Tue, 10 Jun 2025 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/250610-git-stuff/</guid><description>&lt;h1 id="git-for-windows-is-trash">Git for Windows is Trash&lt;/h1>
&lt;p>As you may recall, I find that having a dedicated writing environment is more productive. Getting this blog launched is a serious undertaking because I am building self-hosted infrastructure, while attempting to write about the self-hosed infrastructure, using the self-hosted infrastructure. It&amp;rsquo;s like writing about building a house from bricks while sitting in a house made of sticks that is actively falling down.&lt;/p>
&lt;p>Why is the house falling down? Well, my idea of running a home lab works like this: hack, crash, patch, repeat. Most of the time I am half-way down the rabbit hole before I realize that I took a wrong turn at Albuquerque.&lt;/p></description></item><item><title>The Ouroboros Of Writing About Self-Hosting</title><link>https://chrizzle23.net/posts/250511-ouroboros/ouroboros/</link><pubDate>Wed, 21 May 2025 00:00:00 +0000</pubDate><guid>https://chrizzle23.net/posts/250511-ouroboros/ouroboros/</guid><description>&lt;h1 id="writing-is-still-hard">Writing is &lt;em>still&lt;/em> hard&lt;/h1>
&lt;p>I am trying to document the build of a system from inside the system that I am building, while I am teaching myself to build that system. This method is, as the Irish would say, &lt;em>not the best&lt;/em>. In the past &lt;a href="https://chrizzle23.net/posts/hugo-themes-part-1/#the-tragedy-of-hugo">I bemoaned trying to learn&lt;/a> about git, VSCode, markdown, Caddy, and Hugo all at the same time. In the end I decided to abandon &lt;a href="https://git-scm.com/book/en/v2">learning about git&lt;/a> for another day.&lt;/p></description></item></channel></rss>