summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-03-30 22:50:43 +0200
committerPaul Buetow <paul@buetow.org>2024-03-30 22:50:43 +0200
commit23621ff336841d56164bc3f320bba7e617ae720a (patch)
tree542e5d8e3c154cfa859986af862da637896781ab
parentd0a054c645584383aa19ce71cffe8dd0d283e712 (diff)
Update content for html
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html2
-rw-r--r--gemfeed/atom.xml4
-rw-r--r--index.html2
-rw-r--r--uptime-stats.html2
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) |_:_:_|--&#39;`-. ,--. ksh under-water (((\&#39;/
<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&#39;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&#39;t part of the OpenBSD base system, but I coded my own monigoring system in Go.)</li>
-<li>Don&#39;t configure everything manually. The configuration should be automated and reproducible. (This isn&#39;t part of the OpenBSD base system, but I didn&#39;t need to install any external package on OpenBSD either.)</li>
+<li>Don&#39;t configure everything manually. The configuration should be automated and reproducible. (This isn&#39;t part of the OpenBSD base system, but I didn&#39;t need to install any external software on OpenBSD either.)</li>
</ul><br />
<h2 style='display: inline'>My HA solution</h2><br />
<br />
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 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
- <updated>2024-03-30T22:48:57+02:00</updated>
+ <updated>2024-03-30T22:50:31+02:00</updated>
<title>foo.zone feed</title>
<subtitle>To be in the .zone!</subtitle>
<link href="https://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -66,7 +66,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--&#39;`-. ,--. ksh under-water (((\&#39;/
<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&#39;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&#39;t part of the OpenBSD base system, but I coded my own monigoring system in Go.)</li>
-<li>Don&#39;t configure everything manually. The configuration should be automated and reproducible. (This isn&#39;t part of the OpenBSD base system, but I didn&#39;t need to install any external package on OpenBSD either.)</li>
+<li>Don&#39;t configure everything manually. The configuration should be automated and reproducible. (This isn&#39;t part of the OpenBSD base system, but I didn&#39;t need to install any external software on OpenBSD either.)</li>
</ul><br />
<h2 style='display: inline'>My HA solution</h2><br />
<br />
diff --git a/index.html b/index.html
index bf80f332..290424fa 100644
--- a/index.html
+++ b/index.html
@@ -10,7 +10,7 @@
<body>
<h1 style='display: inline'>foo.zone</h1><br />
<br />
-<span class='quote'>This site was generated at 2024-03-30T22:48:57+02:00 by <span class='inlinecode'>Gemtexter</span></span><br />
+<span class='quote'>This site was generated at 2024-03-30T22:50:31+02:00 by <span class='inlinecode'>Gemtexter</span></span><br />
<br />
<pre>
|\---/|
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 @@
<body>
<h1 style='display: inline'>My machine uptime stats</h1><br />
<br />
-<span class='quote'>This site was last updated at 2024-03-30T22:48:57+02:00</span><br />
+<span class='quote'>This site was last updated at 2024-03-30T22:50:31+02:00</span><br />
<br />
<span>The following stats were collected via <span class='inlinecode'>uptimed</span> on all of my personal computers over many years and the output was generated by <span class='inlinecode'>guprecords</span>, the global uptime records stats analyser of mine.</span><br />
<br />