From 8c3f4d29f72bbdb146d9a06c99209eea0d305b9d Mon Sep 17 00:00:00 2001 From: squid Date: Thu, 12 Nov 2026 19:06:28 +0100 Subject: [PATCH] feat: add the status page news and publish the site on every push to main - add the news post about status.kmalloc.org - document the automatic publishing in the README --- README.md | 4 +++- content/en/news/2026-11-12-status-page.md | 18 ++++++++++++++++++ 2 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 content/en/news/2026-11-12-status-page.md diff --git a/README.md b/README.md index 137bfdf..02fa528 100644 --- a/README.md +++ b/README.md @@ -47,4 +47,6 @@ The post is published at `/news/slug.html`. News are English only: the Italian p ## Publishing -I check every page with the Nu HTML Checker, then copy the output to the web root on the server. +Pushing to `main` publishes the site. A post-receive hook in the Forgejo repository touches a trigger file, `deploy-kmalloc-site.path` on the server notices it and runs `deploy-kmalloc-site`, which builds `main` into a temporary directory and mirrors it into the web root. If the build fails nothing is copied. + +I check every page with the Nu HTML Checker before pushing. diff --git a/content/en/news/2026-11-12-status-page.md b/content/en/news/2026-11-12-status-page.md new file mode 100644 index 0000000..ae14d66 --- /dev/null +++ b/content/en/news/2026-11-12-status-page.md @@ -0,0 +1,18 @@ +--- +title: Status page with Uptime Kuma +summary: The state of every kmalloc.org service is now public at status.kmalloc.org. +--- + +kmalloc.org now has a status page, run with [Uptime Kuma](https://github.com/louislam/uptime-kuma): [status.kmalloc.org](https://status.kmalloc.org/). + +## What it checks + +Every minute it tests the website, webmail and mailing lists, git over HTTPS and SSH, Mastodon, the XMPP and Matrix servers with their web clients, and video conferences. For email it also tests IMAP, SMTP submission and incoming SMTP. + +## What it cannot tell you + +The checks run on the same server as the services. If the whole server goes down, the status page goes down with it. A silent status page is a sign of trouble too. + +## Same rules as the rest + +The page uses no trackers, and it is public and read only. The dashboard behind it is not reachable from the Internet.