aboutsummaryrefslogtreecommitdiff
path: root/content/posts/2023-08-22-comments-2.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/posts/2023-08-22-comments-2.md')
-rw-r--r--content/posts/2023-08-22-comments-2.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/content/posts/2023-08-22-comments-2.md b/content/posts/2023-08-22-comments-2.md
index 9e5df20..dd97bba 100644
--- a/content/posts/2023-08-22-comments-2.md
+++ b/content/posts/2023-08-22-comments-2.md
@@ -2,6 +2,8 @@
title: "Comments 2"
date: 2023-08-22T14:48:41+01:00
draft: false
+params:
+ 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/).