|
| 1 | +# Example configuration file, it's safe to copy this as the default config file without any modification. |
| 2 | + |
| 3 | +# You don't have to copy this file to your instance, |
| 4 | +# just run `./act_runner generate-config > config.yaml` to generate a config file. |
| 5 | + |
| 6 | +log: |
| 7 | + # The level of logging, can be trace, debug, info, warn, error, fatal |
| 8 | + level: info |
| 9 | + |
| 10 | +runner: |
| 11 | + # Where to store the registration result. |
| 12 | + file: .runner |
| 13 | + # Execute how many tasks concurrently at the same time. |
| 14 | + capacity: 1 |
| 15 | + # Extra environment variables to run jobs. |
| 16 | + envs: |
| 17 | + A_TEST_ENV_NAME_1: a_test_env_value_1 |
| 18 | + A_TEST_ENV_NAME_2: a_test_env_value_2 |
| 19 | + # Extra environment variables to run jobs from a file. |
| 20 | + # It will be ignored if it's empty or the file doesn't exist. |
| 21 | + env_file: .env |
| 22 | + # The timeout for a job to be finished. |
| 23 | + # Please note that the Gitea instance also has a timeout (3h by default) for the job. |
| 24 | + # So the job could be stopped by the Gitea instance if it's timeout is shorter than this. |
| 25 | + timeout: 3h |
| 26 | + # The timeout for the runner to wait for running jobs to finish when shutting down. |
| 27 | + # Any running jobs that haven't finished after this timeout will be cancelled. |
| 28 | + shutdown_timeout: 0s |
| 29 | + # Whether skip verifying the TLS certificate of the Gitea instance. |
| 30 | + insecure: true |
| 31 | + # The timeout for fetching the job from the Gitea instance. |
| 32 | + fetch_timeout: 5s |
| 33 | + # The interval for fetching the job from the Gitea instance. |
| 34 | + fetch_interval: 2s |
| 35 | + # The labels of a runner are used to determine which jobs the runner can run, and how to run them. |
| 36 | + # Like: "macos-arm64:host" or "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest" |
| 37 | + # Find more images provided by Gitea at https://gitea.com/gitea/runner-images . |
| 38 | + # If it's empty when registering, it will ask for inputting labels. |
| 39 | + # If it's empty when execute `daemon`, will use labels in `.runner` file. |
| 40 | + labels: |
| 41 | + - "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest" |
| 42 | + - "ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04" |
| 43 | + - "ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04" |
| 44 | + |
| 45 | +cache: |
| 46 | + # Enable cache server to use actions/cache. |
| 47 | + enabled: true |
| 48 | + # The directory to store the cache data. |
| 49 | + # If it's empty, the cache data will be stored in $HOME/.cache/actcache. |
| 50 | + dir: "" |
| 51 | + # The host of the cache server. |
| 52 | + # It's not for the address to listen, but the address to connect from job containers. |
| 53 | + # So 0.0.0.0 is a bad choice, leave it empty to detect automatically. |
| 54 | + host: "" |
| 55 | + # The port of the cache server. |
| 56 | + # 0 means to use a random available port. |
| 57 | + port: 0 |
| 58 | + # The external cache server URL. Valid only when enable is true. |
| 59 | + # If it's specified, act_runner will use this URL as the ACTIONS_CACHE_URL rather than start a server by itself. |
| 60 | + # The URL should generally end with "/". |
| 61 | + external_server: "" |
| 62 | + |
| 63 | +container: |
| 64 | + # Specifies the network to which the container will connect. |
| 65 | + # Could be host, bridge or the name of a custom network. |
| 66 | + # If it's empty, act_runner will create a network automatically. |
| 67 | + network: "" |
| 68 | + # Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker). |
| 69 | + privileged: false |
| 70 | + # And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway). |
| 71 | + options: |
| 72 | + # The parent directory of a job's working directory. |
| 73 | + # NOTE: There is no need to add the first '/' of the path as act_runner will add it automatically. |
| 74 | + # If the path starts with '/', the '/' will be trimmed. |
| 75 | + # For example, if the parent directory is /path/to/my/dir, workdir_parent should be path/to/my/dir |
| 76 | + # If it's empty, /workspace will be used. |
| 77 | + workdir_parent: |
| 78 | + # Volumes (including bind mounts) can be mounted to containers. Glob syntax is supported, see https://github.com/gobwas/glob |
| 79 | + # You can specify multiple volumes. If the sequence is empty, no volumes can be mounted. |
| 80 | + # For example, if you only allow containers to mount the `data` volume and all the json files in `/src`, you should change the config to: |
| 81 | + # valid_volumes: |
| 82 | + # - data |
| 83 | + # - /src/*.json |
| 84 | + # If you want to allow any volume, please use the following configuration: |
| 85 | + # valid_volumes: |
| 86 | + # - '**' |
| 87 | + valid_volumes: [] |
| 88 | + # overrides the docker client host with the specified one. |
| 89 | + # If it's empty, act_runner will find an available docker host automatically. |
| 90 | + # If it's "-", act_runner will find an available docker host automatically, but the docker host won't be mounted to the job containers and service containers. |
| 91 | + # If it's not empty or "-", the specified docker host will be used. An error will be returned if it doesn't work. |
| 92 | + docker_host: "" |
| 93 | + # Pull docker image(s) even if already present |
| 94 | + force_pull: true |
| 95 | + # Rebuild docker image(s) even if already present |
| 96 | + force_rebuild: false |
| 97 | + |
| 98 | +host: |
| 99 | + # The parent directory of a job's working directory. |
| 100 | + # If it's empty, $HOME/.cache/act/ will be used. |
| 101 | + workdir_parent: |
0 commit comments