From 8937d2c6ccd1c77cfe027b60d01a9f608025e469 Mon Sep 17 00:00:00 2001 From: Freyja Odinthrir Date: Wed, 17 Jan 2024 14:54:37 -0800 Subject: [PATCH] Update old blog post --- ...t_automating-some-things.md => automating-some-things.md} | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) rename content/2023/06/28/{_draft_automating-some-things.md => automating-some-things.md} (92%) diff --git a/content/2023/06/28/_draft_automating-some-things.md b/content/2023/06/28/automating-some-things.md similarity index 92% rename from content/2023/06/28/_draft_automating-some-things.md rename to content/2023/06/28/automating-some-things.md index 5bf9e32..f40a3f6 100644 --- a/content/2023/06/28/_draft_automating-some-things.md +++ b/content/2023/06/28/automating-some-things.md @@ -1,7 +1,8 @@ -title: (DRAFT) Automating some things... +title: Automating some things... description: Automating some stuff tags: automation, gitops, freebsd date: 2023-06-28 12:00 +edited: 2024-01-17 14:50 # Automating some things... @@ -20,6 +21,8 @@ Well, we can do a couple things here... Naturally, we choose 2. (There are of course more options, but I won't list them here. Because I haven't thought of them. Not cus they don't exist.) The idea goes like this: since we only need to push static files to update the webserver, I'll just keep the static files in a git repo. Then I can devise a method whereupon updates pushed to the repo are propagated to the webserver automatically via scripts, instead of doing all that manual nonsense each time. +__EDIT 2024-01-17 14:51:__ as of this edit, gitops is achieved. This blog is updated automatically upon a `git commit` to the main branch of a git repo. This is done with gitea actions, and SSH. It is all quite convenient and I'm proud of the achievement. See more [here](../../../2024/01/17/post-01.md) and [here](https://docs.raer.me/02_cicd/ci-cd.html). + --- __EDIT: 2024-01-17 11:34:__