readme fixes
This commit is contained in:
parent
ef39c7a4d1
commit
16e167bcfd
@ -10,8 +10,9 @@ docker build -t cerc/act-runner:local .
|
||||
```
|
||||
|
||||
#### Deploy Gitea Stack
|
||||
1. `cd ./gitea`
|
||||
1. `cd ../act-runner`
|
||||
1. Build the task executor container: `docker build -t cerc/act-runner-task-executor:local -f Dockerfile.task-executor .`
|
||||
1. `cd ../gitea`
|
||||
1. Run the script `./run-this-first.sh`
|
||||
1. Bring up the gitea cluster `docker compose up -d`
|
||||
1. Run the script `./initialize-gitea.sh`
|
||||
@ -29,4 +30,4 @@ Details on how to setup remote debugging of the gitea server inside its containe
|
||||
#### Action Runners
|
||||
|
||||
A Dockerized action runner is deployed by default for the labels `ubuntu-latest` and `ubuntu-22.04`. Details on deploying
|
||||
additional runners can be found [here](../act-runner/act-runner.md).
|
||||
additional runners can be found [here](act-runner.md).
|
||||
|
@ -11,7 +11,7 @@ The following example uses `gitea/act_runner` 0.2.6 to deploy a runner on macOS
|
||||
|
||||
> Note: Runners can be registered globally for an entire Gitea instance, for a specific organization, or for a single repo. This example registers globally.
|
||||
|
||||
Before executing the runner, first obtain a registration token by visiting http://gitea.local:3000/admin/actions/runners, clicking the 'Create new Runner' button, and copying the displayed
|
||||
Before executing the runner, first obtain a registration token by visiting [/admin/actions/runners](http://gitea.local:3000/admin/actions/runners), clicking the 'Create new Runner' button, and copying the displayed
|
||||
registration token, for example, `FTyMBkcK9ErmD0wm8LfBzfXOUUlQA7dBJF6BB64Z`.
|
||||
|
||||
### Runner Registration and Startup
|
||||
|
Loading…
Reference in New Issue
Block a user