commit 0513bbfbb548336ff674deeabcd263942a3044f3
parent 0ad76244be3f6c641cc123adb7101cbbfe3a393d
Author: Eamon Caddigan <eamon.caddigan@gmail.com>
Date: Fri, 6 Dec 2024 22:09:44 -0800
Update the December Adventure log for day 6
Diffstat:
1 file changed, 24 insertions(+), 0 deletions(-)
diff --git a/content/december-adventure/2024-06/index.md b/content/december-adventure/2024-06/index.md
@@ -0,0 +1,24 @@
+---
+title: "2024, Day 6: More fun with Git website stuff"
+description: "Planning to change how I publish my site"
+date: 2024-12-06T21:37:43-08:00
+draft: false
+---
+
+I [previously mentioned]({{< relref "december-adventure/2024-02" >}}) that
+I use `git push` to publish my site, but it's pretty hacky; I basically have
+a makeshift "publish my site" script shoehorned into a hook somewhere. I aim
+to change that.
+
+[My webhost](https://nearlyfreespeech.net/) already has Hugo installed; the
+version's only a bit older than the one I have locally, so that shouldn't
+cause too many headaches. I bet I can streamline my setup and push to
+a remote that lives there, and use a `post-receive` hook to rebuild the site
+in place. I didn't set things up this way initially because I didn't know
+about Git's "[push to
+deploy](https://github.blog/open-source/git/git-2-3-has-been-released/#push-to-deploy)"
+capability, which is enabled by setting Git's configuration option
+`receive.denyCurrentBranch` to `updateInstead` on the "server" repository.
+
+I need to do more testing, but my next update should hopefully have a brief
+writeup on how to set everything up.