hosting/README.md at e4690d4742924ea3234d513e4996c477bb422c96

Thomas E Lackey e4690d4742 Split act-runner into its own pod. (#71 )

```
$ laconic-so --stack act-runner deploy init --output act-runner.yml

$ laconic-so --stack act-runner deploy create --spec-file act-runner.yml --deployment-dir ~/opt/deployments/act-runner-1
$ echo "CERC_GITEA_RUNNER_REGISTRATION_TOKEN=FOO" >> ~/opt/deployments/act-runner-1/config.env
$ laconic-so deployment --dir ~/opt/deployments/act-runner-1 up
```

Reviewed-on: #71
Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Co-committed-by: Thomas E Lackey <telackey@bozemanpass.com>

2023-10-27 18:58:57 +00:00

1.2 KiB

Raw Blame History

Deployment Notes

Gitea

Build gitea/act_runner Docker Container

To build the act_runner container from Gitea, in another directory run:

git clone https://gitea.com/gitea/act_runner
cd act_runner
docker build -t cerc/act-runner:local .

Deploy Gitea Stack

cd ./gitea
Build the task executor container: docker build -t cerc/act-runner-task-executor:local -f Dockerfile.task-executor .
Run the script ./run-this-first.sh
Bring up the gitea cluster docker compose up -d
Run the script ./initialize-gitea.sh
Note the access token printed, it will be needed to publish packages.

Debugging

Gitea server logs can be seen via docker logs . To enable more verbose log output add an environment variable definition like:

GITEA__log__LEVEL=TRACE

to the server definition in docker-compose.yml and re-start. Details on how to setup remote debugging of the gitea server inside its container can be found here.

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.

1.2 KiB Raw Blame History