2022-04-27 04:45:53 -05:00
# act runner
2022-11-24 10:40:00 -06:00
Act runner is a runner for Gitea based on [act ](https://gitea.com/gitea/act ).
2022-10-07 07:59:02 -05:00
2022-11-24 02:34:29 -06:00
## Quickstart
2022-10-07 07:59:02 -05:00
2022-11-24 09:19:25 -06:00
### Build
2022-10-07 07:59:02 -05:00
2022-11-24 09:19:25 -06:00
```bash
2022-11-24 02:34:29 -06:00
make build
2022-10-07 07:59:02 -05:00
```
2022-11-24 02:34:29 -06:00
2022-11-24 09:19:25 -06:00
### Register
2022-11-24 02:34:29 -06:00
2022-11-24 09:19:25 -06:00
```bash
2022-11-24 02:34:29 -06:00
./act_runner register
```
And you will be asked to input:
2022-11-24 10:40:00 -06:00
1. Gitea instance URL, like `http://192.168.8.8:3000/` . You should use your gitea instance ROOT_URL as the instance argument
and you should not use `localhost` or `127.0.0.1` as instance IP;
2. Runner token, you can get it from `http://192.168.8.8:3000/admin/runners` ;
2022-11-24 02:34:29 -06:00
3. Runner name, you can just leave it blank;
4. Runner labels, you can just leave it blank.
The process looks like:
2022-11-24 09:19:25 -06:00
2022-11-24 02:34:29 -06:00
```text
INFO Registering runner, arch=amd64, os=darwin, version=0.1.5.
WARN Runner in user-mode.
INFO Enter the Gitea instance URL (for example, https://gitea.com/):
2022-11-24 10:40:00 -06:00
http://192.168.8.8:3000/
2022-11-24 02:34:29 -06:00
INFO Enter the runner token:
fe884e8027dc292970d4e0303fe82b14xxxxxxxx
INFO Enter the runner name (if set empty, use hostname:Test.local ):
INFO Enter the runner labels, leave blank to use the default labels (comma-separated, for example, ubuntu-20.04:docker://node:16-bullseye,ubuntu-18.04:docker://node:16-buster):
2022-11-24 10:40:00 -06:00
INFO Registering runner, name=Test.local, instance=http://192.168.8.8:3000/, labels=[ubuntu-latest:docker://node:16-bullseye ubuntu-22.04:docker://node:16-bullseye ubuntu-20.04:docker://node:16-bullseye ubuntu-18.04:docker://node:16-buster].
2022-11-24 02:34:29 -06:00
DEBU Successfully pinged the Gitea instance server
INFO Runner registered successfully.
```
2022-11-24 10:40:00 -06:00
You can also register with command line arguments.
```bash
./act_runner register --instance http://192.168.8.8:3000 --token < my_runner_token > --no-interactive
```
If the registry succeed, it will run immediately. Next time, you could run the runner directly.
2022-11-24 09:19:25 -06:00
### Run
2022-11-24 02:34:29 -06:00
2022-11-24 09:19:25 -06:00
```bash
2022-11-24 02:34:29 -06:00
./act_runner daemon
```