From 5d7fbcc47fced289b72edbb5ddde2eb4f99b8203 Mon Sep 17 00:00:00 2001 From: josh-stengg Date: Mon, 5 Aug 2024 00:34:56 +0000 Subject: [PATCH 1/2] Clarify the valid values for COMPRESSION_LEVEL (#42) Remove the comment that values must be preceded with a `-` and add details about default and Huffman compression along with links to the Golang documentation. Reviewed-on: https://gitea.com/gitea/docs/pulls/42 Reviewed-by: Lunny Xiao Co-authored-by: josh-stengg Co-committed-by: josh-stengg --- docs/administration/logging-config.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/administration/logging-config.md b/docs/administration/logging-config.md index 30dffafc..4b86712f 100644 --- a/docs/administration/logging-config.md +++ b/docs/administration/logging-config.md @@ -182,9 +182,8 @@ Settings: `MAX_SIZE_SHIFT` defines the maximum size of a file by left shifting 1 the given number of times (`1 << x`). The exact behavior at the time of v1.17.3 can be seen [here](https://github.com/go-gitea/gitea/blob/v1.17.3/modules/setting/log.go#L185). -The useful values of `COMPRESSION_LEVEL` are from 1 to (and including) 9, where higher numbers mean better compression. +The useful values of `COMPRESSION_LEVEL` are from 1 (best speed) to 9 (best compression). [DefaultCompression](https://pkg.go.dev/compress/gzip#pkg-constants) (-1) and [HuffmanOnly](https://pkg.go.dev/compress/flate#HuffmanOnly) (-2) can also be chosen. Beware that better compression might come with higher resource usage. -Must be preceded with a `-` sign. ### Conn mode From 1cf8f6f58db7df68aec95395d7de0743f601f7d7 Mon Sep 17 00:00:00 2001 From: Matt Van Hest Date: Mon, 5 Aug 2024 03:17:01 +0000 Subject: [PATCH 2/2] Clarified installation instructions between binary package and docker container (#41) Made the act runner installation instructions a little bit clearer when using docker. This distinction was not immediately clear and caused some confusion. Co-authored-by: Jason Song Reviewed-on: https://gitea.com/gitea/docs/pulls/41 Reviewed-by: Jason Song Co-authored-by: Matt Van Hest Co-committed-by: Matt Van Hest --- docs/usage/actions/act-runner.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/usage/actions/act-runner.md b/docs/usage/actions/act-runner.md index 7ed042f8..2fbb956b 100644 --- a/docs/usage/actions/act-runner.md +++ b/docs/usage/actions/act-runner.md @@ -50,6 +50,8 @@ docker pull gitea/act_runner:nightly # for the latest nightly build Configuration is done via a configuration file. It is optional, and the default configuration will be used when no configuration file is specified. +### Binary configuration + You can generate a configuration file by running the following command: ```bash @@ -63,6 +65,8 @@ The default configuration is safe to use without any modification, so you can ju ./act_runner --config config.yaml [command] ``` +### Docker configuration + You could also generate config file with docker: ```bash @@ -115,7 +119,7 @@ Tokens are valid for registering multiple runners, until they are revoked and re ### Register the runner -The act runner can be registered by running the following command: +If this has been installed using the binary package, the act runner can be registered by running the following command: ```bash ./act_runner register @@ -194,6 +198,8 @@ services: - /var/run/docker.sock:/var/run/docker.sock ``` +When using docker, there is no requirement to enter the container and manually run `./act_runner daemon` command as shown below. Once the container has been started successfully, it will show up as an active runner in your Gitea instance. + ### Configuring cache when starting a Runner using docker image If you do not intend to use `actions/cache` in workflow, you can ignore this section.