summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-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 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
diff --git a/index.md b/index.md
index 536f5cb2..cf7a0272 100644
--- a/index.md
+++ b/index.md
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-03-30T22:48:57+02:00 by `Gemtexter`
+> This site was generated at 2024-03-30T22:50:31+02:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.md b/uptime-stats.md
index 9bca9068..3ff2ef25 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:57+02:00
+> This site was last updated at 2024-03-30T22:50:31+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.