From c1c122d4bd329ecbb5330f06507dc4d42b5221fc Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 13 Apr 2024 00:15:08 +0300 Subject: Update content for html --- gemfeed/atom.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'gemfeed/atom.xml') 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 @@ - 2024-04-03T00:06:22+03:00 + 2024-04-12T23:43:12+03:00 foo.zone feed To be in the .zone! @@ -229,8 +229,8 @@ echo "Failover of zone $zone to $MASTER completed"
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).

-https://openbsd.amsterdam
-https://www.hetzner.cloud
+https://OpenBSD.Amsterdam
+https://www.Hetzner.cloud

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.

@@ -246,8 +246,8 @@ echo "Failover of zone $zone to $MASTER completed"
With the DNS failover, HTTP, HTTPS, and Gemini protocols are failovered. This works because all domain virtual hosts are configured on either VM's httpd (OpenBSD's HTTP server) and relayd (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.

-https://man.openbsd.org/httpd.8
-https://man.openbsd.org/relayd.8
+https://man.OpenBSD.org/httpd.8
+https://man.OpenBSD.org/relayd.8

For example, the master is responsible for the https://www.foo.zone and https://foo.zone hosts, whereas the standby can be reached via https://standby.foo.zone (port 80 for plain HTTP works as well). The same principle is followed with all the other hosts, e.g. irregular.ninja, paul.buetow.org and so on. The same applies to my Gemini capsules for https://foo.zone, https://standby.foo.zone, https://paul.buetow.org and https://standby.paul.buetow.org.

@@ -287,7 +287,7 @@ http://www.gnu.org/software/src-highlite --> Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty.

acme.sh.tpl - Rex template for the acme.sh script of mine.
-https://man.openbsd.org/acme-client.1
+https://man.OpenBSD.org/acme-client.1
Let's Encrypt with OpenBSD and Rex

Monitoring


@@ -312,7 +312,7 @@ http://www.gnu.org/software/src-highlite -->
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 (nsd) 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!

-https://www.opensmtpd.org/
+https://www.OpenSMTPD.org/

As a password manager, I use geheim, 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 sync command there.

-- cgit v1.2.3