diff options
| author | Paul Buetow <paul@buetow.org> | 2024-03-30 22:17:10 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-03-30 22:17:10 +0200 |
| commit | b7aabe90f04db707797e867740b67a95e4338b2b (patch) | |
| tree | b03180cecf2279cfb9e200f5a2078205bcf43472 | |
| parent | 5b48f692aa0f1b092340e33f213d754fbd45098b (diff) | |
Update content for html
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | 8 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 12 | ||||
| -rw-r--r-- | index.html | 2 | ||||
| -rw-r--r-- | uptime-stats.html | 2 |
4 files changed, 12 insertions, 12 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 d9d8cfe0..bcb6de38 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html @@ -13,7 +13,7 @@ <span class='quote'>Published at 2024-03-30T22:12:56+02:00</span><br /> <br /> <pre> -Art by Michael J. Penick (mod. by Paul B) +Art by Michael J. Penick (mod. by Paul B.) __________ / nsd tower\ ( @@ -39,17 +39,17 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <br /> <span>I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. </span><br /> <br /> -<span>But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible.</span><br /> +<span>But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible.</span><br /> <br /> <span>It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway.</span><br /> <br /> -<span class='quote'>PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system.</span><br /> +<span class='quote'>PS: ASCII-art reflects an OpenBSD under-water world with all the tools available in the base system.</span><br /> <br /> <h2 style='display: inline'>My auto-failover requirements</h2><br /> <br /> <ul> <li>Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. </li> -<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month).</li> +<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already).</li> <li>It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers.</li> <li>It should be geo-redundant. </li> <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> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index e8a316bf..7d8c460a 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:13:12+02:00</updated> + <updated>2024-03-30T22:16:56+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" /> @@ -15,7 +15,7 @@ <name>Paul Buetow aka snonux</name> <email>paul@dev.buetow.org</email> </author> - <summary>Art by Michael J. Penick (mod. by Paul B)</summary> + <summary>Art by Michael J. Penick (mod. by Paul B.)</summary> <content type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> <h1 style='display: inline'>KISS high-availability with OpenBSD</h1><br /> @@ -23,7 +23,7 @@ <span class='quote'>Published at 2024-03-30T22:12:56+02:00</span><br /> <br /> <pre> -Art by Michael J. Penick (mod. by Paul B) +Art by Michael J. Penick (mod. by Paul B.) __________ / nsd tower\ ( @@ -49,17 +49,17 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <br /> <span>I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like BGP, LVS/IPVS, ldirectord, Pacemaker, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work. </span><br /> <br /> -<span>But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space—something as KISS (keep it simple and stupid) as possible.</span><br /> +<span>But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible.</span><br /> <br /> <span>It would be fine if my personal website wasn't highly available, but the geek in me wants it anyway.</span><br /> <br /> -<span class='quote'>PS: ASCII-art reflects the OpenBSD under-water world with all the tools available in the base system.</span><br /> +<span class='quote'>PS: ASCII-art reflects an OpenBSD under-water world with all the tools available in the base system.</span><br /> <br /> <h2 style='display: inline'>My auto-failover requirements</h2><br /> <br /> <ul> <li>Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. </li> -<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month).</li> +<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already).</li> <li>It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers.</li> <li>It should be geo-redundant. </li> <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> @@ -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:14:16+02:00 by <span class='inlinecode'>Gemtexter</span></span><br /> +<span class='quote'>This site was generated at 2024-03-30T22:16:56+02:00 by <span class='inlinecode'>Gemtexter</span></span><br /> <br /> <pre> |\---/| diff --git a/uptime-stats.html b/uptime-stats.html index 5e39b742..55a9faae 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:14:16+02:00</span><br /> +<span class='quote'>This site was last updated at 2024-03-30T22:16:56+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 /> |