From 2e92daeb002114239b446cd8e458d1b4208a17e9 Mon Sep 17 00:00:00 2001 From: Jordan Bancino Date: Sat, 13 Jan 2024 10:06:06 -0500 Subject: [PATCH] Update docs/dev/hosting.md --- docs/dev/hosting.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/dev/hosting.md b/docs/dev/hosting.md index f877a01..adf422c 100644 --- a/docs/dev/hosting.md +++ b/docs/dev/hosting.md @@ -24,7 +24,7 @@ The general sequence of steps required for setting up a CI runner is as follows: - **Debian:** `apt install make gcc libssl-dev` - **Alpine:** `apk add make gcc musl-dev openssl-dev` 4. Clone `https://git.telodendria.io/Telodendria/act_runner.git`. -5. Run `go build` in the `act_runner` directory. On NetBSD, you may have to `umount /tmp` first because `/tmp` is by default very small. +5. Run `go build` in the `act_runner` directory. On NetBSD, you may have to `umount /tmp` first because `/tmp` is by default very small. Otherwise, make `/tmp` larger during installation. 2GB should be plenty. 6. Run `./act_runner register` to register the runner. When prompted for the tags, follow following convention: - **Linux Distros:** `linux`, `-v`, `` - **BSD Derivatives:** `bsd`, `-v`, `` @@ -33,3 +33,4 @@ The general sequence of steps required for setting up a CI runner is as follows: - **Others:** `other`, `-v`, `` Where `` is one of `x86` or `x64` for now. ARM runners will be a future project. +7. Run `./act_runner daemon`. \ No newline at end of file