diff options
| author | Paul Buetow <paul@buetow.org> | 2024-04-13 00:15:08 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-04-13 00:15:08 +0300 |
| commit | c1c122d4bd329ecbb5330f06507dc4d42b5221fc (patch) | |
| tree | 9a7cff5f0f1a638576b6c4d02bf464dbaf508920 | |
| parent | db1470db2394c5bb02ff5f697952e13ebeb5716a (diff) | |
Update content for html
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html | 12 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 14 | ||||
| -rw-r--r-- | heading.ttf | bin | 0 -> 58448 bytes | |||
| -rw-r--r-- | index.html | 2 | ||||
| -rw-r--r-- | style.css | 27 | ||||
| -rw-r--r-- | text.ttf | bin | 367144 -> 75152 bytes | |||
| -rw-r--r-- | uptime-stats.html | 2 |
7 files changed, 25 insertions, 32 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 0aeb6a35..1d966e04 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.html @@ -219,8 +219,8 @@ echo <font color="#FF0000">"Failover of zone $zone to $MASTER completed"</font> <br /> <span>I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany).</span><br /> <br /> -<a class='textlink' href='https://openbsd.amsterdam'>https://openbsd.amsterdam</a><br /> -<a class='textlink' href='https://www.hetzner.cloud'>https://www.hetzner.cloud</a><br /> +<a class='textlink' href='https://OpenBSD.Amsterdam'>https://OpenBSD.Amsterdam</a><br /> +<a class='textlink' href='https://www.Hetzner.cloud'>https://www.Hetzner.cloud</a><br /> <br /> <span>I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required.</span><br /> <br /> @@ -236,8 +236,8 @@ echo <font color="#FF0000">"Failover of zone $zone to $MASTER completed"</font> <br /> <span>With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's <span class='inlinecode'>httpd</span> (OpenBSD's HTTP server) and <span class='inlinecode'>relayd</span> (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entries, which VM receives the requests.</span><br /> <br /> -<a class='textlink' href='https://man.openbsd.org/httpd.8'>https://man.openbsd.org/httpd.8</a><br /> -<a class='textlink' href='https://man.openbsd.org/relayd.8'>https://man.openbsd.org/relayd.8</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/httpd.8'>https://man.OpenBSD.org/httpd.8</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/relayd.8'>https://man.OpenBSD.org/relayd.8</a><br /> <br /> <span>For example, the master is responsible for the <span class='inlinecode'>https://www.foo.zone</span> and <span class='inlinecode'>https://foo.zone</span> hosts, whereas the standby can be reached via <span class='inlinecode'>https://standby.foo.zone</span> (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. <span class='inlinecode'>irregular.ninja</span>, <span class='inlinecode'>paul.buetow.org</span> and so on. The same applies to my Gemini capsules for <span class='inlinecode'>gemini://foo.zone</span>, <span class='inlinecode'>gemini://standby.foo.zone</span>, <span class='inlinecode'>gemini://paul.buetow.org</span> and <span class='inlinecode'>gemini://standby.paul.buetow.org</span>.</span><br /> <br /> @@ -277,7 +277,7 @@ http://www.gnu.org/software/src-highlite --> <span>Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty.</span><br /> <br /> <a class='textlink' href='https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl'><span class='inlinecode'>acme.sh.tpl</span> - Rex template for the <span class='inlinecode'>acme.sh</span> script of mine.</a><br /> -<a class='textlink' href='https://man.openbsd.org/acme-client.1'>https://man.openbsd.org/acme-client.1</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/acme-client.1'>https://man.OpenBSD.org/acme-client.1</a><br /> <a class='textlink' href='./2022-07-30-lets-encrypt-with-openbsd-and-rex.html'>Let's Encrypt with OpenBSD and Rex</a><br /> <br /> <h3 style='display: inline'>Monitoring</h3><br /> @@ -302,7 +302,7 @@ http://www.gnu.org/software/src-highlite --> <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 /> +<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 cb4e7ee3..a498bc70 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-04-03T00:06:22+03:00</updated> + <updated>2024-04-12T23:43:12+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" /> @@ -229,8 +229,8 @@ echo <font color="#FF0000">"Failover of zone $zone to $MASTER completed"</font> <br /> <span>I am renting two small OpenBSD VMs: One at OpenBSD Amsterdam and the other at Hetzner Cloud. So, both VMs are hosted at another provider, in different IP subnets, and in different countries (the Netherlands and Germany).</span><br /> <br /> -<a class='textlink' href='https://openbsd.amsterdam'>https://openbsd.amsterdam</a><br /> -<a class='textlink' href='https://www.hetzner.cloud'>https://www.hetzner.cloud</a><br /> +<a class='textlink' href='https://OpenBSD.Amsterdam'>https://OpenBSD.Amsterdam</a><br /> +<a class='textlink' href='https://www.Hetzner.cloud'>https://www.Hetzner.cloud</a><br /> <br /> <span>I only have a little traffic on my sites. I could always upload the static content to AWS S3 if I suddenly had to. But this will never be required.</span><br /> <br /> @@ -246,8 +246,8 @@ echo <font color="#FF0000">"Failover of zone $zone to $MASTER completed"</font> <br /> <span>With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's <span class='inlinecode'>httpd</span> (OpenBSD's HTTP server) and <span class='inlinecode'>relayd</span> (it's also part of OpenBSD and I use it to TLS offload the Gemini protocol). So, both VMs accept requests for all the hosts. It's just a matter of the DNS entries, which VM receives the requests.</span><br /> <br /> -<a class='textlink' href='https://man.openbsd.org/httpd.8'>https://man.openbsd.org/httpd.8</a><br /> -<a class='textlink' href='https://man.openbsd.org/relayd.8'>https://man.openbsd.org/relayd.8</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/httpd.8'>https://man.OpenBSD.org/httpd.8</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/relayd.8'>https://man.OpenBSD.org/relayd.8</a><br /> <br /> <span>For example, the master is responsible for the <span class='inlinecode'>https://www.foo.zone</span> and <span class='inlinecode'>https://foo.zone</span> hosts, whereas the standby can be reached via <span class='inlinecode'>https://standby.foo.zone</span> (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. <span class='inlinecode'>irregular.ninja</span>, <span class='inlinecode'>paul.buetow.org</span> and so on. The same applies to my Gemini capsules for <span class='inlinecode'>https://foo.zone</span>, <span class='inlinecode'>https://standby.foo.zone</span>, <span class='inlinecode'>https://paul.buetow.org</span> and <span class='inlinecode'>https://standby.paul.buetow.org</span>.</span><br /> <br /> @@ -287,7 +287,7 @@ http://www.gnu.org/software/src-highlite --> <span>Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty.</span><br /> <br /> <a class='textlink' href='https://codeberg.org/snonux/rexfiles/src/branch/master/frontends/scripts/acme.sh.tpl'><span class='inlinecode'>acme.sh.tpl</span> - Rex template for the <span class='inlinecode'>acme.sh</span> script of mine.</a><br /> -<a class='textlink' href='https://man.openbsd.org/acme-client.1'>https://man.openbsd.org/acme-client.1</a><br /> +<a class='textlink' href='https://man.OpenBSD.org/acme-client.1'>https://man.OpenBSD.org/acme-client.1</a><br /> <a class='textlink' href='./2022-07-30-lets-encrypt-with-openbsd-and-rex.html'>Let's Encrypt with OpenBSD and Rex</a><br /> <br /> <h3 style='display: inline'>Monitoring</h3><br /> @@ -312,7 +312,7 @@ http://www.gnu.org/software/src-highlite --> <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 /> +<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/heading.ttf b/heading.ttf Binary files differnew file mode 100644 index 00000000..a2917114 --- /dev/null +++ b/heading.ttf @@ -10,7 +10,7 @@ <body> <h1 style='display: inline'>foo.zone</h1><br /> <br /> -<span class='quote'>This site was generated at 2024-04-03T23:50:16+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> +<span class='quote'>This site was generated at 2024-04-13T00:14:52+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> <br /> <pre> |\---/| @@ -4,6 +4,11 @@ } @font-face { + font-family: 'heading'; + src: url("./heading.ttf") format("truetype"); +} + +@font-face { font-family: 'code'; src: url("./code.ttf") format("truetype"); } @@ -19,19 +24,14 @@ } body { - font-family: text, monospace; + font-family: text, sans-serif; max-width: 1024px; - padding: 20px 20px; + padding: 10px 10px; margin: 20px auto; - border-image: linear-gradient(#f6b73c, #4d9f0c) 30; - border-width: 1px; - border-style: solid; } h1, h2, h3 { - background: -webkit-linear-gradient(#f6b73c, #4d9f0c); - -webkit-background-clip: text; - -webkit-text-fill-color: transparent; + font-family: heading, serif; } a { @@ -88,21 +88,14 @@ img { pre { font-family: code, monospace; - padding: 0; overflow-x: auto; - scrollbar-width: none; - margin-left: 23px; - margin-right: 23px; - padding: 23px; - border-image: linear-gradient(#f6b73c, #4d9f0c) 30; - border-width: 3px; - border-style: solid; + padding-left: 23px; color: grey; + border-left: dashed grey; } span.inlinecode { font-family: code, monospace; - border: 1px solid #000000; padding: 1px; color: grey; } Binary files differdiff --git a/uptime-stats.html b/uptime-stats.html index a59cae1e..855a6636 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-04-03T23:50:16+03:00</span><br /> +<span class='quote'>This site was last updated at 2024-04-13T00:14:52+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 /> |
