From 79b14946585618ef76120d72d7ebd69f12e5b3c0 Mon Sep 17 00:00:00 2001 From: Vlad Date: Mon, 23 Jun 2025 12:48:08 +0100 Subject: [PATCH] Fixed image links --- ...age 20250622224303.png => gitea_secret_setup.png | Bin notes/0000-how-this-was-built.md | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename Pasted image 20250622224303.png => gitea_secret_setup.png (100%) diff --git a/Pasted image 20250622224303.png b/gitea_secret_setup.png similarity index 100% rename from Pasted image 20250622224303.png rename to gitea_secret_setup.png diff --git a/notes/0000-how-this-was-built.md b/notes/0000-how-this-was-built.md index efa03a8..0ace79b 100644 --- a/notes/0000-how-this-was-built.md +++ b/notes/0000-how-this-was-built.md @@ -232,7 +232,7 @@ Good practice says that I should add some resource limits and requests, but I'll I'm running a local Gitea instance, so I just created a new [repo](https://k3gtpi.jumpingcrab.com/vlad/vlads-notes) and saved the K8s cluster config as a repo secret called "K8S_CONF" (use secrets instead of plain variables as the latter can be exposed in the action's logs) -![[Pasted image 20250622224303.png]] +![[gitea_secret_setup.png]] I then created the ".gitea/workflows" directories and placed the workflow YAML file (publish.yaml) within. The workflow is split into two jobs: - 1st job