From 92787c159262a57fa20b2eb05ed710e1e6cfca96 Mon Sep 17 00:00:00 2001 From: Martin Ashby Date: Mon, 25 Mar 2024 21:36:21 +0000 Subject: Final conversion to Zine --- content/posts/2023-08-22-comments-2.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'content/posts/2023-08-22-comments-2.md') diff --git a/content/posts/2023-08-22-comments-2.md b/content/posts/2023-08-22-comments-2.md index dd97bba..2e028a8 100644 --- a/content/posts/2023-08-22-comments-2.md +++ b/content/posts/2023-08-22-comments-2.md @@ -1,9 +1,9 @@ --- -title: "Comments 2" -date: 2023-08-22T14:48:41+01:00 -draft: false -params: - comments: true +.title = "Comments 2", +.author = "Martin Ashby", +.date = @date("2023-08-22T14:48:41+01:00"), +.layout = "single.html", +.custom = {"comments": true}, --- [Previously](/posts/2022-12-30-comments/) I added a basic comment system to my website using a separate web server which served only the comment HTML. This is fine, but it does require another program running continuously on my server. Since that server is a raspberry pi, and it is running a lot of other software as well, and my blog doesn't get a lot of hits (let alone comments), I thought I could do better by using the [Common Gateway Interface (CGI)](https://en.wikipedia.org/wiki/Common_Gateway_Interface). CGI doesn't require a daemon program, but instead will launch a program to generate dynamic content when someone loads the page. In this way, no memory or CPU is required until an actual page is requested. The downside is that a new process is launched for each page load, but I think that's an OK trade-off for me. I already have CGI configured on my web server for running [cgit](/posts/2022-12-31-cgit/). -- cgit v1.2.3-ZIG