summaryrefslogtreecommitdiff
path: root/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl')
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl10
1 files changed, 5 insertions, 5 deletions
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 f1af4277..6dcfc242 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
@@ -193,7 +193,7 @@ The authorative nameserver for my domains runs on both VMs, and both are configu
Check out the whole script here:
-=> https://codeberg.org/snonux/conf/src/branch/master/frontends/scripts/dns-failover.ksh dns-failover.ksh
+=> https://github.com/snonux/conf/src/branch/master/frontends/scripts/dns-failover.ksh dns-failover.ksh
### Fairly cheap and geo-redundant
@@ -252,7 +252,7 @@ The ACME automation is yet another daily CRON script `/usr/local/bin/acme.sh`. I
Let's encrypt certificates usually expire after 3 months, so a weekly failover of my VMs is plenty.
-=> https://codeberg.org/snonux/conf/src/branch/master/frontends/scripts/acme.sh.tpl `acme.sh.tpl` - Rex template for the `acme.sh` script of mine.
+=> https://github.com/snonux/conf/src/branch/master/frontends/scripts/acme.sh.tpl `acme.sh.tpl` - Rex template for the `acme.sh` script of mine.
=> https://man.OpenBSD.org/acme-client.1
=> ./2022-07-30-lets-encrypt-with-openbsd-and-rex.gmi Let's Encrypt with OpenBSD and Rex
@@ -260,7 +260,7 @@ Let's encrypt certificates usually expire after 3 months, so a weekly failover o
CRON is sending me an E-Mail whenever a failover is performed (or whenever a failover failed). Furthermore, I am monitoring my DNS servers and hosts through Gogios, the monitoring system I have developed.
-=> https://codeberg.org/snonux/gogios
+=> https://github.com/snonux/gogios
=> ./2023-06-01-kiss-server-monitoring-with-gogios.gmi KISS server monitoring with Gogios
Gogios, as I developed it by myself, isn't part of the OpenBSD base system.
@@ -270,7 +270,7 @@ Gogios, as I developed it by myself, isn't part of the OpenBSD base system.
I use Rexify, a friendly configuration management system that allows automatic deployment and configuration.
=> https://www.rexify.org
-=> https://codeberg.org/snonux/conf/src/branch/master/frontends codeberg.org/snonux/rexfiles/frontends
+=> https://github.com/snonux/conf/src/branch/master/frontends github.com/snonux/rexfiles/frontends
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!
@@ -282,7 +282,7 @@ Other high-available services running on my OpenBSD VMs are my MTAs for mail for
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.
-=> https://codeberg.org/snonux/geheim
+=> https://github.com/snonux/geheim
E-Mail your comments to `paul@nospam.buetow.org` :-)