From 23621ff336841d56164bc3f320bba7e617ae720a Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 30 Mar 2024 22:50:43 +0200 Subject: Update content for html --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | 2 +- gemfeed/atom.xml | 4 ++-- index.html | 2 +- uptime-stats.html | 2 +- 4 files changed, 5 insertions(+), 5 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 (((\'/
  • 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/gemfeed/atom.xml b/gemfeed/atom.xml index 08599cf7..251c5dc7 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2024-03-30T22:48:57+02:00 + 2024-03-30T22:50:31+02:00 foo.zone feed To be in the .zone! @@ -66,7 +66,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/
  • 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.html b/index.html index bf80f332..290424fa 100644 --- a/index.html +++ b/index.html @@ -10,7 +10,7 @@

    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.html b/uptime-stats.html
index 1c3bfbf3..fcb29a6a 100644
--- a/uptime-stats.html
+++ b/uptime-stats.html
@@ -10,7 +10,7 @@
 
 
    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.
    
 
    
-- 
cgit v1.2.3