hosting

History

Roy Crihfield f9bfee788f Fix last gitea compose command		2023-09-05 11:16:28 +08:00
..
config	Update config to remove warning in runner log	2023-05-25 02:30:03 -06:00
delete-repo.sh	Repo management scripts	2023-05-01 13:23:32 -06:00
docker-compose.yml	Bump gitea to 1.20	2023-07-18 11:21:05 -06:00
Dockerfile.task-executor	Update for latest act_runner. (#29 )	2023-04-11 15:04:59 -05:00
gitea-debugging.md	Add documentation on debugging Gitea	2023-05-27 11:53:58 -06:00
initialize-gitea.sh	Fix last gitea compose command	2023-09-05 11:16:28 +08: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

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.