logoalt Hacker News

cobertostoday at 2:54 PM1 replyview on HN

It's based on act[0] so it's quite like GitHub actions but not completely [1].

I found in the current version of Forgejo the most secure way to set it up was just to put the runner on a different host. There's a Docker in Docker setup [2] that was challenging to get working correctly but still didn't quite feel secure...

After setting it all up, I'm convinced GitHub actions as a concept is flawed. I wish the community would make a simpler git-defined CI/CD that didn't have the crazy surface area that actions does... Named shell scripts that can call out to other stuff in the runner Docker image and report it to the UI would be a nice start.

[0]: https://github.com/nektos/act

[1]: https://forgejo.org/docs/v15.0/user/actions/github-actions/#...

[2]: https://forgejo.org/docs/v15.0/admin/actions/docker-access/#...


Replies

dborehamtoday at 3:08 PM

Agreed. GitHub Actions feels like someone's science project created while on a mushroom trip. Really you just want a thing that executes a shell script in a runner.