cerc-io/hosting
16
0
Fork 0
Code Issues 7 Pull Requests 2 Packages Projects Releases Wiki Activity
064d221ecc
hosting/gitea
History
David Boreham 064d221ecc Behave better when init script is re-run (#61) 
Reviewed-on: #61
Co-authored-by: David Boreham <david@bozemanpass.com>
Co-committed-by: David Boreham <david@bozemanpass.com>
2023-10-04 18:47:14 +00:00
..
config Configure runner cache (#57) 2023-10-04 12:26:10 -05:00
delete-repo.sh Repo management scripts 2023-05-01 13:23:32 -06:00
docker-compose.yml Configure runner cache (#57) 2023-10-04 12:26:10 -05:00
Dockerfile.task-executor Use modern node.js install scheme 2023-09-28 06:19:39 -06:00
gitea-debugging.md Add documentation on debugging Gitea 2023-05-27 11:53:58 -06:00
initialize-gitea.sh Behave better when init script is re-run (#61) 2023-10-04 18:47:14 +00:00
migrate-repo.sh Repo management scripts 2023-05-01 13:23:32 -06:00
README.md Add link to debugging doc 2023-06-22 08:15:59 -06:00
run-this-first.sh Fix directory name 2023-04-08 16:55:23 -06:00

README.md

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.