summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-03-30 23:00:54 +0200
committerPaul Buetow <paul@buetow.org>2024-03-30 23:00:54 +0200
commit3c1273840565f16fb717a6c75a478ad3555bce4f (patch)
tree5d7fd827c527be201568c34c3a3398b857577fe6
parente1c1287b029c0475b2ab11763b011e406bec18de (diff)
Update content for md
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md2
-rw-r--r--index.md2
-rw-r--r--uptime-stats.md2
3 files changed, 3 insertions, 3 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
diff --git a/index.md b/index.md
index 23396e52..e9b26123 100644
--- a/index.md
+++ b/index.md
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-03-30T22:55:25+02:00 by `Gemtexter`
+> This site was generated at 2024-03-30T23:00:41+02:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.md b/uptime-stats.md
index 0b13dd85..b7affcd5 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:55:25+02:00
+> This site was last updated at 2024-03-30T23:00:41+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.