diff options
| author | Paul Buetow <paul@buetow.org> | 2024-03-30 22:50:43 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-03-30 22:50:43 +0200 |
| commit | 0cab33385a30fa70c628da947da65c9ec385db9f (patch) | |
| tree | 2262fa55d6d3b326c0cb136313c19848f5f34d3d /gemfeed | |
| parent | ada9cfa1d37c61c7ff86cd28af2935151757b1cb (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 36031420..f5f0a126 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -45,7 +45,7 @@ It would be fine if my personal website wasn't highly available, but the geek in * 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.) -* 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 package on OpenBSD either.) +* 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 |