diff options
| -rw-r--r-- | gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md | 14 | ||||
| -rw-r--r-- | index.md | 2 | ||||
| -rw-r--r-- | uptime-stats.md | 2 |
3 files changed, 12 insertions, 6 deletions
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md index 54733209..2bc5f162 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md @@ -44,8 +44,8 @@ It would be fine if my personal website wasn't highly available, but the geek in * 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. * Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available. * Let's Encrypt TLS certificates should always work (before and after a failover). -* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. (This isn't part of the OpenBSD base system, but I coded my own monitoring system in Go.) -* Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base system, but I didn't need to install any external software on OpenBSD either.) +* Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover. +* Don't configure everything manually. The configuration should be automated and reproducible. ## My HA solution @@ -259,7 +259,9 @@ CRON is sending me an E-Mail whenever a failover is performed (or whenever a fai [https://codeberg.org/snonux/gogios](https://codeberg.org/snonux/gogios) [KISS server monitoring with Gogios](./2023-06-01-kiss-server-monitoring-with-gogios.md) - + +Gogios, as I developed it by myself, isn't part of the OpenBSD base system. + ### Rex automation I use Rexify, a friendly configuration management system that allows automatic deployment and configuration. @@ -267,9 +269,13 @@ I use Rexify, a friendly configuration management system that allows automatic d [https://www.rexify.org](https://www.rexify.org) [codeberg.org/snonux/rexfiles/frontends](https://codeberg.org/snonux/rexfiles/src/branch/master/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! + ## More HA -Other high-available services running on my OpenBSD VMs are my MTAs for mail forwarding (OpenSMTPD) 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! +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. @@ -1,6 +1,6 @@ # foo.zone -> This site was generated at 2024-03-30T23:38:33+02:00 by `Gemtexter` +> This site was generated at 2024-03-31T11:01:19+03:00 by `Gemtexter` ``` |\---/| diff --git a/uptime-stats.md b/uptime-stats.md index 92b821b0..6e800cd1 100644 --- a/uptime-stats.md +++ b/uptime-stats.md @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2024-03-30T23:38:33+02:00 +> This site was last updated at 2024-03-31T11:01:19+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. |