Hey everyone,

I just set up a self-hosted GitHub Actions runner in my homelab and wrote about it in my self-hosted blog! This is my second blog entry, so I would really appreciate any feedback or suggestions to help improve my writing is more than welcome.

You can check out the post here: https://cachaza.cc/blog/02-self-hosted-ci-cd

  • CameronDev@programming.devEnglish
    1·
    7 days ago

    I can’t find it right now, but there used to be a warning about not self-hosting runners for public repos. Anyone could fork your repo, and the fork would inherit your runners, and then they could change the pipeline to RCE on your runner.

    Has that been fixed?

    I went to a completely private gitlab instead, with mirroring up to github for anything that needed to be public.

    Edit: seems to maybe not be an issue anymore, at the very least it doesn’t seem to affect that repo. Still, for anyone else, make sure forks and MRs can’t cause action to run automatically on your runner, because that would be very bad.