gitea/gitea-docs
1
0
Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2026-07-22 02:37:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'main' of gitea.com:gitea/docs

Browse Source
This commit is contained in:
Lunny Xiao
2024-08-06 16:44:54 -07:00
parent af22422e1a 1cf8f6f58d
commit 54bc810c46
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/administration/logging-config.md
View File

@@ -181,9 +181,8 @@ Settings:
`MAX_SIZE_SHIFT` defines the maximum size of a file by left shifting 1 the given number of times (`1 << x`). `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 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. Beware that better compression might come with higher resource usage.
Must be preceded with a `-` sign.
### Conn mode ### Conn mode

8
docs/usage/actions/act-runner.md
View File

@@ -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. 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: You can generate a configuration file by running the following command:
```bash ```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] ./act_runner --config config.yaml [command]
``` ```
### Docker configuration
You could also generate config file with docker: You could also generate config file with docker:
```bash ```bash
@@ -115,7 +119,7 @@ Tokens are valid for registering multiple runners, until they are revoked and re
### Register the runner ### 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 ```bash
./act_runner register ./act_runner register
@@ -194,6 +198,8 @@ services:
- /var/run/docker.sock:/var/run/docker.sock - /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 ### 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. If you do not intend to use `actions/cache` in workflow, you can ignore this section.