Gitea Actions
-
tried to play with it a bit. enabled actions in the ini, as documented here:
https://blog.gitea.io/2022/12/feature-preview-gitea-actions/
installed a runner binary from the link here:
https://gitea.com/gitea/act_runner (just to try get up and running quicker..)
placed it into /tmp/ on the gitea container, chmod +x, ran it. could successfully register the runner.
actually executing actions seems to fail, because by default, it wants a docker connection. looks like this can be hacked out if one builds a runner by hand:
... obviously, at the price of having no docker available to the actions, which mean some won't work.
but the docker hurdle aside, this is so easy to set up it that it might be worth exploring as part of the app's package..
-
-
@girish yeah, well, since when has following the rules ever been fun?
I would guess that they say that because if your actions misbehave, or want to, they can interfere with the running gitea instance, so yeah, a separate host would be nice. but I don't know if cloudron has the ability to provision multiple containers for a single app?
-
-
https://blog.gitea.io/2023/03/hacking-on-gitea-actions/ is an excellent read.
-
@mario said in Gitea Actions:
Are there plans to offer this as an app?
It's already available, just install and enable the feature in the app.ini as indicated in the blog link above.
If you mean the runners, those are separate and can be run as binaries or containers as per their docs.
