From bfb5d9d45ded0c65404713e3db6c71fa16a98106 Mon Sep 17 00:00:00 2001 From: Alexander Goussas Date: Fri, 1 May 2026 10:46:37 -0500 Subject: [PATCH] refactor: wording --- posts/2026-04-30-how-i-manage-my-blog.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/posts/2026-04-30-how-i-manage-my-blog.md b/posts/2026-04-30-how-i-manage-my-blog.md index 9d45b54..d4524b6 100644 --- a/posts/2026-04-30-how-i-manage-my-blog.md +++ b/posts/2026-04-30-how-i-manage-my-blog.md @@ -3,12 +3,13 @@ title: How I Manage my Blog date: 30 april 2026 --- -There is an accompanying video devlog available on YouTube: https://www.youtube.com/watch?v=c6z5A_PRodg. +There is an accompanying video devlog available on YouTube: +https://www.youtube.com/watch?v=c6z5A_PRodg. Recently I went down the Kubernetes rabbit-hole and automated my whole blog's pipeline. From build to deployment. No GitHub actions or any other 3rd party CI provider. All self-hosted, literally. Well, with the sole exception of -CloudFlare Tunnels, course. +CloudFlare Tunnels, of course. How did I do it? @@ -21,7 +22,7 @@ Docker Hub. This is all automated in my git server, as we'll see in a minute. Next, my stuff is hosted in a git server that I own. This server is exposed via SSH and cloudflare tunnels. I have it configured to only allow public key -authentication and not root login, for example. Also, the SSH port is not +authentication and no root login, for example. Also, the SSH port is not publicly exposed and is only accessible via cloudflared. Now, Git has hooks for both server and client. In this case, we are interested -- 2.43.0