diff options
| author | Paul Buetow <paul@buetow.org> | 2024-03-31 11:01:33 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-03-31 11:01:33 +0300 |
| commit | e636b8f28928ddfd123c251bf2e714738240928d (patch) | |
| tree | 96144d31e812c75384c87e71bc982e5d49b9e9d2 | |
| parent | 36ec0089199363e8aa75dbf7c9ec4576186666ac (diff) | |
Update content for html
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | 14 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 16 | ||||
| -rw-r--r-- | index.html | 2 | ||||
| -rw-r--r-- | uptime-stats.html | 2 |
4 files changed, 23 insertions, 11 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 1a6b1e03..39caba65 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html @@ -55,8 +55,8 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <li>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.</li> <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'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't part of the OpenBSD base system, but I coded my own monitoring system in Go.)</li> -<li>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.)</li> +<li>Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover.</li> +<li>Don't configure everything manually. The configuration should be automated and reproducible.</li> </ul><br /> <h2 style='display: inline'>My HA solution</h2><br /> <br /> @@ -286,7 +286,9 @@ http://www.gnu.org/software/src-highlite --> <br /> <a class='textlink' href='https://codeberg.org/snonux/gogios'>https://codeberg.org/snonux/gogios</a><br /> <a class='textlink' href='./2023-06-01-kiss-server-monitoring-with-gogios.html'>KISS server monitoring with Gogios</a><br /> -<span> </span><br /> +<br /> +<span>Gogios, as I developed it by myself, isn't part of the OpenBSD base system. </span><br /> +<br /> <h3 style='display: inline'>Rex automation</h3><br /> <br /> <span>I use Rexify, a friendly configuration management system that allows automatic deployment and configuration.</span><br /> @@ -294,9 +296,13 @@ http://www.gnu.org/software/src-highlite --> <a class='textlink' href='https://www.rexify.org'>https://www.rexify.org</a><br /> <a class='textlink' href='https://codeberg.org/snonux/rexfiles/src/branch/master/frontends'>codeberg.org/snonux/rexfiles/frontends</a><br /> <br /> +<span>Rex isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either as Rex is invoked from my Laptop!</span><br /> +<br /> <h2 style='display: inline'>More HA</h2><br /> <br /> -<span>Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (<span class='inlinecode'>nsd</span>) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! </span><br /> +<span>Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD - also part of the OpenBSD base system) and the authoritative DNS servers (<span class='inlinecode'>nsd</span>) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! </span><br /> +<br /> +<a class='textlink' href='https://www.opensmtpd.org/'>https://www.opensmtpd.org/</a><br /> <br /> <span>As a password manager, I use <span class='inlinecode'>geheim</span>, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the <span class='inlinecode'>sync</span> command there. </span><br /> <br /> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index e94512ed..999dcb9c 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-30T23:36:52+02:00</updated> + <updated>2024-03-31T11:01:19+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="https://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -65,8 +65,8 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <li>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.</li> <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'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't part of the OpenBSD base system, but I coded my own monitoring system in Go.)</li> -<li>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.)</li> +<li>Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover.</li> +<li>Don't configure everything manually. The configuration should be automated and reproducible.</li> </ul><br /> <h2 style='display: inline'>My HA solution</h2><br /> <br /> @@ -296,7 +296,9 @@ http://www.gnu.org/software/src-highlite --> <br /> <a class='textlink' href='https://codeberg.org/snonux/gogios'>https://codeberg.org/snonux/gogios</a><br /> <a class='textlink' href='./2023-06-01-kiss-server-monitoring-with-gogios.html'>KISS server monitoring with Gogios</a><br /> -<span> </span><br /> +<br /> +<span>Gogios, as I developed it by myself, isn't part of the OpenBSD base system. </span><br /> +<br /> <h3 style='display: inline'>Rex automation</h3><br /> <br /> <span>I use Rexify, a friendly configuration management system that allows automatic deployment and configuration.</span><br /> @@ -304,9 +306,13 @@ http://www.gnu.org/software/src-highlite --> <a class='textlink' href='https://www.rexify.org'>https://www.rexify.org</a><br /> <a class='textlink' href='https://codeberg.org/snonux/rexfiles/src/branch/master/frontends'>codeberg.org/snonux/rexfiles/frontends</a><br /> <br /> +<span>Rex isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either as Rex is invoked from my Laptop!</span><br /> +<br /> <h2 style='display: inline'>More HA</h2><br /> <br /> -<span>Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) and the authoritative DNS servers (<span class='inlinecode'>nsd</span>) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! </span><br /> +<span>Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD - also part of the OpenBSD base system) and the authoritative DNS servers (<span class='inlinecode'>nsd</span>) for all my domains. No particular HA setup is required, though, as the protocols (SMTP and DNS) already take care of the failover to the next available host! </span><br /> +<br /> +<a class='textlink' href='https://www.opensmtpd.org/'>https://www.opensmtpd.org/</a><br /> <br /> <span>As a password manager, I use <span class='inlinecode'>geheim</span>, a command-line tool I wrote in Ruby with encrypted files in a git repository (I even have it installed in Termux on my Phone). For HA reasons, I simply updated the client code so that it always synchronises the database with both servers when I run the <span class='inlinecode'>sync</span> command there. </span><br /> <br /> @@ -10,7 +10,7 @@ <body> <h1 style='display: inline'>foo.zone</h1><br /> <br /> -<span class='quote'>This site was generated at 2024-03-30T23:38:33+02:00 by <span class='inlinecode'>Gemtexter</span></span><br /> +<span class='quote'>This site was generated at 2024-03-31T11:01:19+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> <br /> <pre> |\---/| diff --git a/uptime-stats.html b/uptime-stats.html index 5ae5dafd..fac5e214 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-30T23:38:33+02:00</span><br /> +<span class='quote'>This site was last updated at 2024-03-31T11:01:19+03: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 /> |