Update content for md

1 files changed, 18 insertions, 0 deletions

diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
index f5477fe3..39f0c59c 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
@@ -27,6 +27,24 @@ _____|_:_:_|  (o)-(o)  |_:_:_|--'`-.     ,--. ksh under-water (((\'/
 
 ```
 
+```
+Table of contents:
+    KISS high-availability with OpenBSD
+        My auto-failover requirements
+        My HA solution
+            Only OpenBSD base installation required
+   !/bin/ksh
+    Race condition (e.g. script execution aborted in the middle of the previous run)
+            Fairly cheap and geo-redundant
+            Failover time and split-brain
+            Failover support for multiple protocols
+            Let's encrypt TLS certificates
+    Weekly auto-failover for Let's Encrypt automation
+            Monitoring
+            Rex automation
+        More HA
+```
+
 I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. 
 
 But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible.