From 05eb7a4617a144270d6c8cf70109aa248a822255 Mon Sep 17 00:00:00 2001 From: "Radu C. Martin" Date: Mon, 21 Apr 2025 09:19:25 +0200 Subject: [PATCH] fix(0001): fix typos and line breaks --- content/post/0001-hello-friend/index.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/content/post/0001-hello-friend/index.md b/content/post/0001-hello-friend/index.md index 097c0fb..63a2696 100644 --- a/content/post/0001-hello-friend/index.md +++ b/content/post/0001-hello-friend/index.md @@ -131,17 +131,18 @@ self-contained—easier to install and maintain, which is great for CI. Long story short: I found a Hugo theme similar to Chirpy and migrated everything over even before the blog technically went live. Win-win? -### Infrastructure Both of the themes I looked at are designed for easy GitHub -Pages deployment. Fork the theme, add your content, push—CI/CD handles the -rest. +### Infrastructure +Both of the themes I looked at are designed for easy GitHub Pages deployment. +Fork the theme, add your content, push—CI/CD handles the rest. But where’s the fun in that? Hosting it on GitHub isn't very “old internet”, and I’m already self-hosting my own git forge, so everything’s ready to go. -#### Self-Hosting I had a few options for deployment. My first idea was to go -self-contained: after the site is built, the files get copied into an nginx -container and pushed to my forgejo container registry. Then it’s deployed via -Docker Compose and updated by Renovate. +#### Self-Hosting +I had a few options for deployment. My first idea was to go self-contained: +after the site is built, the files get copied into an nginx container and +pushed to my forgejo container registry. Then it’s deployed via Docker Compose +and updated by Renovate. I tried this—and while it’s straightforward to implement—it didn’t sit well with me. Renovate only updates the digest after a new image is published, so @@ -227,8 +228,8 @@ projects. - No promises about future posts. That **never** works out (I’ll explain why that is… in a future post). -## What to expect, and how often can be expected No expectations. No schedule. -No guarantees of quality or consistency. You’ve been warned. +## What to expect, and how often can be expected +No expectations. No schedule. No guarantees of quality or consistency. **Postscriptum**: I started writing this post on April 7th, but only managed to publish it now. Is that an indicator of how often I'm going to actually publish