diff options
| author | Paul Buetow <paul@buetow.org> | 2024-03-30 23:00:54 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-03-30 23:00:54 +0200 |
| commit | 3c1273840565f16fb717a6c75a478ad3555bce4f (patch) | |
| tree | 5d7fd827c527be201568c34c3a3398b857577fe6 /gemfeed | |
| parent | e1c1287b029c0475b2ab11763b011e406bec18de (diff) | |
Update content for md
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 2 |
1 files changed, 1 insertions, 1 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 6b32eaeb..bbad2f6c 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -44,7 +44,7 @@ It would be fine if my personal website wasn't highly available, but the geek in * It's fine if my sites aren't reachable for five or ten minutes every other month. Due to their static nature, I don't care if there's a split-brain scenario where some requests reach one server and other requests reach another server. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monigoring system in Go.) +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monitoring system in Go.) * Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either.) ## My HA solution |