fix: headers

src/content/posts/software/hosting-a-git-server.mdx

@@ -3,17 +3,17 @@ title: "hosting a git server"
 date: "07/05/2025"
 ---
 
-## why
+# why
 
 No reason. Perhaps to host personal files in the future. AWS's micro free tier is great, too.
 
-## what
+# what
 
 - Write my own git web ui
 - Support clones from my own website
 - Host private files on my git ui
 
-## the process
+# the process
 
 I detail self-hosting a git server on an AWS t2.micro instance ("free" for 1 year) as of May 2025. [Git's instructions](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) were vastly outdated so hopefully this saves a lucky reader some time.
 
@@ -70,7 +70,7 @@ I detail self-hosting a git server on an AWS t2.micro instance ("free" for 1 yea
 
 11. There are a variety of choices for web ui, including [cgit](https://git.zx2c4.com/cgit/), [gitweb](https://git-scm.com/docs/gitweb) (I do not recommend this—the scripts are ancient and require manual tuning), and some even heavier options that allow for further customization. I am not a fan of viewing code on the web, so you cannot in [my custom ui](https://git.barrettruth.com). I spin up a simple python server to walk the projects in `/srv/git` and configured a systemd service to run it in the ec2 box:
 
-## lessons
+# lessons
 
 - **It feels great to do things yourself**: I used GPT-4o for linux server command help, that was about it
 - **Always ask "what is this?" before using something**: this would've saved me hours of realizing a 12 year old perl script should not have been running my git ui.