Add table of contents to old blogs

content/2024/09/06/2024090601.md

@@ -1,6 +1,14 @@
 title: Some changes have ocurred
 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
 
@@ -11,17 +19,17 @@ Server layout has undergone some changes, most notably:
 - how the deployment works
 
 
-## Pi os
+# 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.
 
 The pi now runs openSUSE Leap 15.6.
 
-## How I do gitops
+# How I do gitops
 
 I've more or less solidified how I do gitops. When I need to version control files on a remote server, I make a local git repo with those files that also contains a script which is used to deploy any of said files on the remote server. This is achieved over SSH. A bare git repo is initialized on the remote server, and added as a remote in the gitops repo. Then, that remote is pushed to in a way that it is always synced perfectly with the local copy. Then, a script in the git repo can SSH into the remote, clone the repo from the local copy, and do stuff with the files.
 
-## How the deployment server works.
+# How the deployment server works.
 
 Before, i used rootless docker and usernames to sort of namespace things in an ineffective way. I was also using gitea actions configs to do things on the deployment server with an ssh key that had unlimited access to the user account. This provided a false sense of security.