Remove tables of contents since they don't work, fix base template.

content/2024/09/06/2024090601.md

@@ -3,13 +3,6 @@ tags: servers, server layout, gitops, devops
 date: 2024-09-06 03:27
 edited: 2024-09-27 13:53
 
-# Table of Contents <!-- omit in toc -->
-
-- [Some changes have ocurred](#some-changes-have-ocurred)
-- [Pi os](#pi-os)
-- [How I do gitops](#how-i-do-gitops)
-- [How the deployment server works.](#how-the-deployment-server-works)
-
 # Some changes have ocurred
 
 Server layout has undergone some changes, most notably:
@@ -18,7 +11,6 @@ Server layout has undergone some changes, most notably:
 - how i do gitops
 - how the deployment works
 
-
 # Pi os
 
 I needed docker on my pi, so i abandoned freebsd. It was a good run and taught me a lot about unix. But implementing a custom freebsd server is just. not my thing anymore. Docker is so much easier for versioning. And if i want to compile from scratch? I have that option, too, with docker.

content/2024/09/26/configuration-management.md

@@ -4,13 +4,6 @@ tags: post, git, gitops, devops, cicd, tech, scripting
 date: 2024-09-26 05:21
 edited: 2024-09-27 13:53
 
-# Table of Contents <!-- omit in toc -->
-
-- [Managing homeserver configs](#managing-homeserver-configs)
-- [So how do I do things?](#so-how-do-i-do-things)
-- [conclusion](#conclusion)
-
-
 # Managing homeserver configs
 
 I've run my home services a number of different ways over the years. I've split things between multiple virtual machines, I've set up a 'bare metal ' kubernetes cluster distributed between multiple VMs and hardware devices on my home network. I've used FreeBSD and its Jails to run things I compiled by scratch in an effort to lower attack surface. I ran (and run) VMs and containers on proxmox, truenas core and truenas scale. Each method brings its pros & cons, security tradeoffs, and configuration complexity. Though I've practiced more complex enterprise-level user & permission management (ldap/active directory) techniques, I've settled on "good enough" security practices for my uses/needs (I don't have multiple people accessing things over ssh, for example, so I do the unthinkable and - gasp - ssh directly into root with an ed25519 keypair to administer servers). No SSH ports are exposed directly to the internet anyway - well, except for gitea. But that's also protected with keypairs.

content/2024/09/27/scripts-with-passwords-revisited.md

@@ -3,14 +3,6 @@ description: Another look at my entry from 12th May, 2024 where I explore a meth
 tags: security, scripting, unix, linux
 date: 2024-09-27 12:11
 
-# Table of Contents <!-- omit in toc -->
-
-- [Revisiting an old topic](#revisiting-an-old-topic)
-- [The process](#the-process)
-  - [Obfuscation](#obfuscation)
-  - [Deobfuscation](#deobfuscation)
-- [Conclusion](#conclusion)
-
 # Revisiting an old topic
 
 [In this blog entry dated 12th May, 2024](https://blog.raer.me/2024/05/01/20240512.html) I discuss a method where I'm able to keep passphrases stored inside of a bash script, while still being able to execute the bash script. Its been a few months and I've improved the process for obfuscating/deobfuscating scripts, since I'm now using this method as part of my process in writing/editing backup scripts. Thus I'd like to retouch the topic since rereading the previous blogpost leaves me a bit undersatisfied.