summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-03-30 22:49:04 +0200
committerPaul Buetow <paul@buetow.org>2024-03-30 22:49:04 +0200
commitada9cfa1d37c61c7ff86cd28af2935151757b1cb (patch)
treeec888a219d96e0f51b28176cd00098b6c8de177f
parent3ad4a3576172bfd951c6a1e954fb6168b4bf2d1f (diff)
Update content for md
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md4
-rw-r--r--index.md2
-rw-r--r--uptime-stats.md2
3 files changed, 4 insertions, 4 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 f1668995..36031420 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
@@ -44,8 +44,8 @@ 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)
-* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base syste, but I didn't need to install any external package on OpenBSD either)
+* 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.)
## My HA solution
diff --git a/index.md b/index.md
index 102811f7..536f5cb2 100644
--- a/index.md
+++ b/index.md
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-03-30T22:48:01+02:00 by `Gemtexter`
+> This site was generated at 2024-03-30T22:48:57+02:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.md b/uptime-stats.md
index 4ad16b21..9bca9068 100644
--- a/uptime-stats.md
+++ b/uptime-stats.md
@@ -1,6 +1,6 @@
# My machine uptime stats
-> This site was last updated at 2024-03-30T22:48:01+02:00
+> This site was last updated at 2024-03-30T22:48:57+02:00
The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine.