From 7af68bf6d1a17b73f9c3106fe0fc06aea21eb539 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 2 Apr 2024 01:33:34 +0300 Subject: Update content for gemtext --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi | 4 ++-- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl | 4 ++-- gemfeed/atom.xml | 6 +++--- index.gmi | 2 +- uptime-stats.gmi | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi index c05dbc18..6eb067c5 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi @@ -59,7 +59,7 @@ My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple => https://man.OpenBSD.org/sed => https://man.OpenBSD.org/dig => https://man.OpenBSD.org/ftp -=> https://man.openbsd.org/cron +=> https://man.OpenBSD.org/cron I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. @@ -211,7 +211,7 @@ A split-brain scenario between the old master and the new master might happen. T ### Failover support for multiple protocols -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 entry, which hosts receive the requests. +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 diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl index 370b7ce7..5eb8b001 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl @@ -59,7 +59,7 @@ My HA solution for Web and Gemini is based on DNS (OpenBSD's `nsd`) and a simple => https://man.OpenBSD.org/sed => https://man.OpenBSD.org/dig => https://man.OpenBSD.org/ftp -=> https://man.openbsd.org/cron +=> https://man.OpenBSD.org/cron I also used the `dig` (for DNS checks) and `ftp` (for HTTP/HTTPS checks) programs. @@ -211,7 +211,7 @@ A split-brain scenario between the old master and the new master might happen. T ### Failover support for multiple protocols -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 entry, which hosts receive the requests. +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 diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 7b4bc167..3259fa1a 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2024-03-31T11:01:19+03:00 + 2024-04-02T01:33:21+03:00 foo.zone feed To be in the .zone! @@ -80,7 +80,7 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ https://man.OpenBSD.org/sed
https://man.OpenBSD.org/dig
https://man.OpenBSD.org/ftp
-https://man.openbsd.org/cron
+https://man.OpenBSD.org/cron

I also used the dig (for DNS checks) and ftp (for HTTP/HTTPS checks) programs.

@@ -244,7 +244,7 @@ echo "Failover of zone $zone to $MASTER completed"

Failover support for multiple protocols



-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 entry, which hosts receive the requests.
+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
diff --git a/index.gmi b/index.gmi index 64ef9268..7ad7ff8d 100644 --- a/index.gmi +++ b/index.gmi @@ -1,6 +1,6 @@ # foo.zone -> This site was generated at 2024-03-31T11:01:19+03:00 by `Gemtexter` +> This site was generated at 2024-04-02T01:33:21+03:00 by `Gemtexter` ``` |\---/| diff --git a/uptime-stats.gmi b/uptime-stats.gmi index f26445ad..14bb1990 100644 --- a/uptime-stats.gmi +++ b/uptime-stats.gmi @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2024-03-31T11:01:19+03:00 +> This site was last updated at 2024-04-02T01:33:21+03:00 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine. -- cgit v1.2.3