hosting/gitea
2023-11-08 17:52:14 +00:00
..
act-runner.md Add security warning 2023-10-18 20:16:00 +00:00
delete-repo.sh Repo management scripts 2023-05-01 13:23:32 -06:00
docker-compose-gitea.yml fix package-registry stack 2023-11-08 17:52:14 +00:00
gitea-debugging.md Add documentation on debugging Gitea 2023-05-27 11:53:58 -06:00
initialize-gitea.sh Add comment 2023-10-17 22:44:54 -05:00
migrate-repo.sh Repo management scripts 2023-05-01 13:23:32 -06:00
README.md Split act-runner into its own pod. (#71) 2023-10-27 18:58:57 +00:00
run-this-first.sh Fix directory name 2023-04-08 16:55:23 -06:00

Deployment Notes

Gitea

Build gitea/act_runner Docker Container

  1. 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

  1. cd ./gitea
  2. Build the task executor container: docker build -t cerc/act-runner-task-executor:local -f Dockerfile.task-executor .
  3. Run the script ./run-this-first.sh
  4. Bring up the gitea cluster docker compose up -d
  5. Run the script ./initialize-gitea.sh
  6. 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.