Forgejo runner - alpha release, should not be considered secure enough to deploy in production
3d78433564
Fix #64 (incompletely). It's still not ideal. It makes more sense to use the gateway IP address of container network as outbound IP of cache server. However, this requires act to cooperate, some think like: - act creates the network for new container, and returns the network to runner. - runner extracts the gateway IP in the network. - runner uses the gateway IP as outbound IP, and pass it to act as cache server endpoint. - act It continues to create the container with the created network. Reviewed-on: https://gitea.com/gitea/act_runner/pulls/74 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> |
||
---|---|---|
.forgejo/workflows | ||
.gitea/workflows | ||
artifactcache | ||
client | ||
cmd | ||
config | ||
core | ||
engine | ||
poller | ||
register | ||
runtime | ||
.dockerignore | ||
.gitignore | ||
.golangci.yml | ||
build.go | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
Makefile | ||
README.md |
Forgejo Actions runner
Runs workflows found in .forgejo/workflows
, using a format similar to GitHub actions but with a Free Software implementation.
It is compatible with Forgejo v1.19.0-0-rc0