Remove tables of contents since they don't work, fix base template.
This commit is contained in:
@@ -4,16 +4,6 @@ Date: 2024-01-17 10:28
|
||||
Tags: personal, gitops, devops, technical
|
||||
Edited: 2024-09-27 13:50
|
||||
|
||||
# Table of Contents <!-- omit in toc -->
|
||||
|
||||
- [A new post for a new blog](#a-new-post-for-a-new-blog)
|
||||
- [Fixing that old mess](#fixing-that-old-mess)
|
||||
- [Static Site Generation](#static-site-generation)
|
||||
- [Using blag](#using-blag)
|
||||
- [Automation](#automation)
|
||||
- [Conclusion](#conclusion)
|
||||
|
||||
|
||||
# A new post for a new blog
|
||||
|
||||
This is a personal project built... because i can. I have this odd fascination with the concept of `gitops` - that is, keeping entire codebases + their documentation within a single self-contained git repository. I also have an interest in self-hosting my own services/infrastructure because it gives me a better fundamental understanding of the hardware/software behind things like `GitHub Actions`. Thus, instead of being run/deployed with any number of cloud services, i've done my best to self-host my own stuff.
|
||||
|
||||
@@ -3,21 +3,6 @@ description: Some seafood tacos.
|
||||
tags: cooking, recipes
|
||||
date: 2024-01-19 05:59
|
||||
|
||||
# Table of Contents <!-- omit in toc -->
|
||||
|
||||
- [Baja Tacos](#baja-tacos)
|
||||
- [Ingredients](#ingredients)
|
||||
- [Fresh](#fresh)
|
||||
- [Spices](#spices)
|
||||
- [Protein](#protein)
|
||||
- [Directions](#directions)
|
||||
- [Prep](#prep)
|
||||
- [Slaw](#slaw)
|
||||
- [Sauce](#sauce)
|
||||
- [Rub](#rub)
|
||||
- [Assemble](#assemble)
|
||||
|
||||
|
||||
# Baja Tacos
|
||||
|
||||
## Ingredients
|
||||
|
||||
@@ -4,15 +4,6 @@ tags: baking, cooking, cheesecake, recipes
|
||||
date: 2024-01-18 12:05
|
||||
edited: 2024-09-27 13:52
|
||||
|
||||
# Table of Contents <!-- omit in toc -->
|
||||
|
||||
- [New York style cheesecake](#new-york-style-cheesecake)
|
||||
- [Ingredients](#ingredients)
|
||||
- [For the Crust](#for-the-crust)
|
||||
- [For the Filling](#for-the-filling)
|
||||
- [Directions](#directions)
|
||||
- [How to Slice Cheesecake](#how-to-slice-cheesecake)
|
||||
|
||||
# New York style cheesecake
|
||||
|
||||
Shamelessly stolen from [martha stewart dot com](https://www.marthastewart.com/865202/new-york-style-cheesecake). Thanks `Lucinda Scala Quinn` for a great recipe!
|
||||
|
||||
@@ -4,12 +4,6 @@ tags: technical, gitops, devops
|
||||
date: 2024-01-18 01:09
|
||||
edited: 2024-09-27 13:52
|
||||
|
||||
# Table of Contents <!-- omit in toc -->
|
||||
|
||||
- [Increasing Complexity](#increasing-complexity)
|
||||
- [Actually doing the thing](#actually-doing-the-thing)
|
||||
- [Getting my fork on my package repo](#getting-my-fork-on-my-package-repo)
|
||||
|
||||
# Increasing Complexity
|
||||
|
||||
__START TIME: 2024-01-18 01:09__
|
||||
|
||||
@@ -3,14 +3,6 @@ description: A very tasty rice and veggies recipe.
|
||||
tags: cooking
|
||||
date: 2024-01-31 18:45
|
||||
|
||||
# Table of Contents <!-- omit in toc -->
|
||||
|
||||
- [Mediterranean style rice](#mediterranean-style-rice)
|
||||
- [Ingredeints](#ingredeints)
|
||||
- [Spices](#spices)
|
||||
- [Cooking fat](#cooking-fat)
|
||||
- [Cooking instructions](#cooking-instructions)
|
||||
|
||||
# Mediterranean style rice
|
||||
|
||||
This recipe is inspired by a rice dish served by a mediterranean restaurant I used to go to in my hometown.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -40,9 +40,9 @@
|
||||
|
||||
<footer>
|
||||
Copyleft 🄯 Freyja R. L. Odinthrir 2024 all wrongs reserved.
|
||||
<br>
|
||||
Subscribe to the <a href="/atom.xml">atom feed</a>.
|
||||
<br>
|
||||
Copyright
|
||||
<!-- Contact me via
|
||||
<a rel="me" href="https://mastodon.social/[FIXME]">[FIXME] Mastodon</a> or
|
||||
<a href="https://github.com/[FIXME]">[FIXME] Github</a>.
|
||||
|
||||
Reference in New Issue
Block a user