diff options
| author | Paul Buetow <paul@buetow.org> | 2024-03-30 22:48:15 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2024-03-30 22:48:15 +0200 |
| commit | 0b9acc87801f5b9937c235b0475d5abbbdf6d2b5 (patch) | |
| tree | 3399ff99081c5a7bf78b7573bf991c675befa7ed /gemfeed/atom.xml | |
| parent | cc31b26e623240d89c1399130743a62f6e46e05f (diff) | |
Update content for gemtext
Diffstat (limited to 'gemfeed/atom.xml')
| -rw-r--r-- | gemfeed/atom.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 23527403..fe2206f8 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-03-30T22:42:12+02:00</updated> + <updated>2024-03-30T22:47:35+02:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -59,14 +59,14 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/ <br /> <ul> <li>Be OpenBSD-based (I prefer OpenBSD because of the cleanliness and good documentation) and rely on as few external packages as possible. </li> -<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already).</li> +<li>Don't rely on the hottest and newest tech (don't want to migrate everything to a new and fancier technology next month already!).</li> <li>It should be reasonably cheap. I want to avoid paying a premium for floating IPs or fancy Elastic Load Balancers.</li> <li>It should be geo-redundant. </li> <li>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.</li> <li>Failover should work for both HTTP/HTTPS and Gemini protocols. My self-hosted MTAs and DNS servers should also be highly available.</li> <li>Let's Encrypt TLS certificates should always work (before and after a failover).</li> -<li>Have good monitoring in place so I know when a failover was performed and when something went wrong with the failover.</li> -<li>Don't configure everything manually. The configuration should be automated and reproducible.</li> +<li>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 monigoring system in Go)</li> +<li>Don't configure everything manually. The configuration should be automated and reproducible. (This isn't part of the OpenBSD base syste, but I didn't need to install any external package on OpenBSD either)</li> </ul><br /> <h2 style='display: inline'>My HA solution</h2><br /> <br /> |