From 4a3d53bd5f438074af4bf8996406e7c0ecbc9eaa Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Fri, 16 May 2025 21:22:08 -0600 Subject: [PATCH] Update blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md --- blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md b/blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md index 7d8e9a5..4bb5cfa 100644 --- a/blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md +++ b/blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md @@ -65,7 +65,7 @@ container_engine: "" ``` ### Runner Workflow Task Files -When it comes to telling the runner what to do and how to do it, you create what are called runner "**Workflows**". These files reside within `/.gitea/workflows` and are `.yaml` format. You can have multiple workflows for one repository, with different flows that fire-off on different runners. An example of the flow used to replace Git-Repo-Updater's functionality can be seen below. +When it comes to telling the runner what to do and how to do it, you create what are called runner "**Workflows**". These files reside within `/.gitea/workflows` and are `.yaml` format. If you have any familiarity with Ansible, the similarities are staggaring. You can have multiple workflows for one repository, with different flows that fire-off on different runners. An example of the flow used to replace Git-Repo-Updater's functionality can be seen below. In the workflow below, it spins up a runner within the Alpine Linux environment that the `docker.io/gitea/act_runner:latest` uses, then installs NodeJS, Git, and Rsync for the core functionality that mirrors Git-Repo-Updater: