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 | 23621ff336841d56164bc3f320bba7e617ae720a (patch) | |
| tree | 542e5d8e3c154cfa859986af862da637896781ab /gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | |
| parent | d0a054c645584383aa19ce71cffe8dd0d283e712 (diff) | |
Update content for html
Diffstat (limited to 'gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html')
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html index ce95624f..c54395e4 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html @@ -56,7 +56,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <li>Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available.</li> <li>Let's Encrypt TLS certificates should always work (before and after a failover).</li> <li>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.)</li> -<li>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.)</li> +<li>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.)</li> </ul><br /> <h2 style='display: inline'>My HA solution</h2><br /> <br /> |