From 5c72efc6c53d7c1a8f78f453cdfa42e0092d148e Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 12 Nov 2026 18:57:12 -0500 Subject: [PATCH] docs: full apply command for the proposed host runner Refs #45 Co-Authored-By: Claude Opus 5.5 --- docs/ci-cd/runner.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/ci-cd/runner.md b/docs/ci-cd/runner.md index af5b269..7073c12 100644 --- a/docs/ci-cd/runner.md +++ b/docs/ci-cd/runner.md @@ -205,7 +205,8 @@ I3 and S3: run the runner on `inspiron-3670` instead of in the cluster. variables as the in-cluster runner. Host-only ones are `gitea_actions_host_*` in the role's `defaults/main.yml`: 4 CPUs and 16 GB for jobs, and a CPU weight below the host's other containers. -- **Apply.** `ansible-playbook ci-runner.yaml`. The first run fetches a +- **Apply.** `ansible-playbook -i inventories/eom.dev.yml ci-runner.yaml -K` + (`-K` because the host asks for a sudo password). The first run fetches a registration token from the cluster, registers, and deletes the token file. Rerunning recreates only containers whose settings changed; that cancels a running job.