<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bash on Chrizzle23.net</title><link>https://chrizzle23.net/tags/bash/</link><description>Recent content in Bash 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>Wed, 11 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://chrizzle23.net/tags/bash/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>