systemd runner labels

docs/developer/cicd_runner.md

@@ -22,6 +22,9 @@ cd ~/gitea-runner
 /usr/local/bin/act_runner register --instance https://gitea.psi.ch/ --labels hla-dev --token <token> --no-interactive
 ```
 
+Note, if you use a systemd service with a config file as in the example below, 
+the labels will be read from that file.
+
 This generates a `.runner` file.
 
 
@@ -42,20 +45,6 @@ tar -xf node-v20.11.1-linux-x64.tar.xz --strip-components=2 -C ~/.local/bin/ nod
 rm node-v20.11.1-linux-x64.tar.xz
 ```
 
-Change the location of the working directory (uv .venvs are built here, take up lots of space)
-
-```
-mkdir -p /sls/bd/hla/.cache/act
-```
-
-and edit `/etc/act_runner/config.yaml`
-
-```
-host:
-  # The parent directory of a job's working directory.
-  # If it's empty, $HOME/.cache/act/ will be used.
-  workdir_parent: "/sls/bd/hla/.cache/act"
-```
 
 ## Manually run the runner
 
@@ -120,6 +109,29 @@ SocketMode=0660
 SocketGroup=podman
 ```
 
+Change the location of the working directory (uv .venvs are built here, take up lots of space)
+
+```
+mkdir -p /sls/bd/hla/.cache/act
+```
+
+and edit `/etc/act_runner/config.yaml`
+
+```
+host:
+  # The parent directory of a job's working directory.
+  # If it's empty, $HOME/.cache/act/ will be used.
+  workdir_parent: "/sls/bd/hla/.cache/act"
+```
+
+Configure the runner labels: (edit `/etc/act_runner/config.yaml`)
+
+```
+runner:
+  labels:
+    - "hla-dev"
+```
+
 Enable and restart:
 
 ```