Add Draft Post on GitOps

content/posts/BookReview-UnixProgEnv.md

@@ -1,5 +1,5 @@
 ---
-title: "Book Review: The UNIX Programming Enviroment"
+title: "Book Review: The UNIX Programming Environment"
 date: 2023-12-27
 toc: false
 images:
@@ -11,13 +11,13 @@ tags:
 
 ![Cover Photo](/images/unix_prog_env.jpg)
 
-"The UNIX Programming Enviroment" in many ways feels like the quintessential guide to the UNIX philosophy and operating system. It's very well written, and holds up to this very day. Readers somewhat familar with UNIX already may consider skipping the first chapter, as it's mostly review on the basic UNIX commands. The sections on shell scripting were a bit vague in areas, but it served its purpose regardless.
+"The UNIX Programming Environment" in many ways feels like the quintessential guide to the UNIX philosophy and operating system. It's very well written, and holds up to this very day. Readers somewhat familiar with UNIX already may consider skipping the first chapter, as it's mostly review on the basic UNIX commands. The sections on shell scripting were a bit vague in areas, but it served its purpose regardless.
 
 I especially appreciated the sections devoted to Yacc and Lex, as I never really realized the importance of those particular tools in the development of scripting languages (including /bin/sh) and compilers. It felt very well written given the inherent complexities in script parsing and tokenization. 
 
 The chapter on Troff and Nroff was also quite good, however, it was a bit manual-like at times, which wasn't the case for the rest of the book. I especially appreciated the effort in trying to focus on specific examples and usecases instead of writing all of the possible methods and utilities. 
 
-I'd recomend this book to anyone who deals with UNIX-like systems on a regular basis, or if you're interested in some practical knowledge + some historical tidbits about the original UNIX operating system.
+I'd recommend this book to anyone who deals with UNIX-like systems on a regular basis, or if you're interested in some practical knowledge + some historical tidbits about the original UNIX operating system.
 
 #### Coming Soon...
 Thanks for reading! My next writings will either be about ["UNIX: A History and Memoir"](https://search.worldcat.org/title/1125982089), or CTF write-ups for [37C3's Potluck CTF](https://play.potluckctf.com/). 

content/posts/My Homelab (Part 1).md

@@ -67,7 +67,7 @@ With the hardware decisions made, it was time to finally breathe some life into
 
 The server rack took center stage, positioned for easy access to ports and cables. Cable management is also important for any setup, ensuring a clean and organized appearance. Do not underestimate the impact of a well-organized space. It not only enhances functionality but also contributes to a more enjoyable experience later down the line. My management approach definitely left some stuff to be desired, however it certainly works well enough for my needs.
 ### 4.2 Power and Cooling
-Power and cooling are often overlooked aspects of a home lab, but they are critical for the stability and the longevity of your equipment, as well as the safety of your data. I did not invest in a uninterruptible power supply (UPS), however I would strongly recomend doing so to safeguard against power fluctuations and outages. The majority of my improvement plans (at the current moment) involve the implementation of better reliability using devices like UPS's. Additionally, you may want to consider the implentation of a cooling solution to maintain optimal operating conditions, especially during heavy workloads. My requirements and hardware didn't nessitate this, especially given the cool temps of my basement.
+Power and cooling are often overlooked aspects of a home lab, but they are critical for the stability and the longevity of your equipment, as well as the safety of your data. I did not invest in a uninterruptible power supply (UPS), however I would strongly recommend doing so to safeguard against power fluctuations and outages. The majority of my improvement plans (at the current moment) involve the implementation of better reliability using devices like UPS's. Additionally, you may want to consider the implementation of a cooling solution to maintain optimal operating conditions, especially during heavy workloads. My requirements and hardware didn't nessitate this, especially given the cool temps of my basement.
 
 ### 4.3 Initial Configuration
 With the physical organization and setup complete, it was time to power up the hardware for the first time. This phase involved a lot of sitting on the ground messing with cables and install wizards. I didn't encounter much resistance during the process, but it's definitely normal to encounter challenges during the initial configuration. Patience and a systematic approach are key. Getting the initial setup right can make the configuration later-on a lot easier or harder depending on the scenario.

content/posts/SSH-Configuration.md

@@ -140,7 +140,7 @@ Once you've found a good balance of security and usability that works for you, y
 You can find more complete versions of these playbooks, configurations, and other assorted scripts/utilities at: https://github.com/benjaminhays/homelab-automation/
 
 **P.S.**
-Sorry for the long delay in articles being posted, curricular responsibilites gave me little time to work on my blog. Should hopefully be more regular in coming weeks/months
+Sorry for the long delay in articles being posted, curricular responsibilities gave me little time to work on my blog. Should hopefully be more regular in coming weeks/months
 
 [^1]: https://thenewstack.io/the-terrapin-attack-a-new-threat-to-ssh-integrity/
 [^2]: https://github.com/jtesta/ssh-audit

content/posts/ansible-gitea-gitops.md

@@ -0,0 +1,16 @@
+---
+title: "Efficient and Secure GitOps using Gitea, Ansible, and Github Actions"
+date: 2024-07-01
+draft: true
+description: The Polyfill supply chain attack highlights critical security vulnerabilities in the web ecosystem. What can be done to secure open-source dependencies and mitigate supply chain risks?
+tags:
+  - Security
+  - DevOps
+  - Network Automation
+---
+
+I run a pretty small homelab, for what it's worth. I have about 4 LXC containers and two QEMU virtual machines running at any given time, the majority of which just serve as convenient frontends to store my data.
+
+![Picture of my Proxmox Container List](/images/proxmox-machines.png)
+
+Despite the fact that I manage so few servers and services for my needs, I still find myself wanting some way to deploy changes across all of my machines simultaneously. For this purpose, I have used and maintained a set of Ansible playbooks which, for the most part, have suited my workflow.

hugo.toml

@@ -11,7 +11,6 @@ tag = 'tags'
 
 [params]
 footerContent = '<a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0</a>'
-#customCSS = ["/css/style.css"]
 
 paginationSize = 20
 homeCollectionTitle = 'Posts'

themes/typo

@@ -1 +1 @@
-Subproject commit a08607f9a1fba8dfc19da7e26198c1f6420f9e2c
+Subproject commit 3692440a512006860adc7dbfb826f36e086ca2c9