Add caching for Gitea Actions, improve performance
This commit is contained in:
@@ -2,6 +2,20 @@
|
||||
|
||||
This file is used to list changes made in each version of the kosmos_gitea cookbook.
|
||||
|
||||
# 0.2.2
|
||||
|
||||
- Add `config.yaml` for the gitea actions runner, enabling the built-in cache
|
||||
server (listening on the Docker bridge gateway `172.17.0.1`) and bumping
|
||||
`runner.capacity` to 2 for concurrent job execution. Each runner gets a unique
|
||||
cache port derived from `cache_base_port` (8088) + its index in the runners
|
||||
data bag.
|
||||
- Set `container.network` to a user-defined Docker bridge network
|
||||
(`gitea-actions`, subnet `172.20.0.0/16`) so job containers get DNS resolution
|
||||
for service containers (e.g. `redis`) while keeping the cache server reachable
|
||||
at the network gateway `172.20.0.1`.
|
||||
- Open the cache port in the firewall for Docker bridge traffic
|
||||
(`172.20.0.0/16`), fixing `Request timeout` errors from `actions/cache`.
|
||||
|
||||
# 0.1.0
|
||||
|
||||
Initial release.
|
||||
|
||||
Reference in New Issue
Block a user