act_runner: A runner for Gitea based on act.
-
Used in the context of Gitea Actions, their version of GitHub Actions.
From the fact that Cloudron is used by many to reduce costs (by renting less VPSs), it'd be pretty useful to be able to host such an application on Cloudron.I've made a package of the binary @ https://github.com/Lanhild/act-runner-cloudron. Though, some aspects that bring issues:
- Can't have a proper healthcheck (I have no idea what the binary uses as a port)
- 2 runtime options; Docker or binary. They suggest to use the docker option. Though, it needs access to the docker socket.
- Runner registration to Gitea instance; the runner has to "register" to a Gitea instance using a token provided by the latter. Then the runner pings the instance and checks to validate the response.
This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid
.runnerregistration file. -
Used in the context of Gitea Actions, their version of GitHub Actions.
From the fact that Cloudron is used by many to reduce costs (by renting less VPSs), it'd be pretty useful to be able to host such an application on Cloudron.I've made a package of the binary @ https://github.com/Lanhild/act-runner-cloudron. Though, some aspects that bring issues:
- Can't have a proper healthcheck (I have no idea what the binary uses as a port)
- 2 runtime options; Docker or binary. They suggest to use the docker option. Though, it needs access to the docker socket.
- Runner registration to Gitea instance; the runner has to "register" to a Gitea instance using a token provided by the latter. Then the runner pings the instance and checks to validate the response.
This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid
.runnerregistration file.This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid
.runnerregistration file.I have solved this issue by checking if the registration file exists. If it doesn't, I simply start the runner's cache-server. The instruction to register the runner is explained in the post install message.
-
This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid
.runnerregistration file.I have solved this issue by checking if the registration file exists. If it doesn't, I simply start the runner's cache-server. The instruction to register the runner is explained in the post install message.
-
@Lanhild I'm still having issue with the healthcheck, though.Solved it by removing an unused param
