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

  • EccTM@lemmy.mlEnglish
    6·
    5 days ago

    That’s cool. Any reason why you went with a self-hosted GitHub runner over making the full jump to a self-hosted Gitea instance + runner?

      • ikidd@lemmy.worldEnglish
        1·
        5 days ago

        I tried this last week and it wasn’t very good. It was poorly documented, and when it failed out on a simple java CI, I just went back to act.

        • EccTM@lemmy.mlEnglish
          1·
          4 days ago

          Yeah, the Forgejo documentation was dreadful when I last looked, it really showed its origin as a Gitea replacement for people already using (and understanding) Gitea.

    • Cachvza@lemmy.worldOPEnglish
      1·
      4 days ago

      My main reason was honestly laziness 😅 . I just went with what was quickest to set up. I also hadn’t realiced I could have two upstreams on my repo: one public-facing on GitHub (because I’m still in college and trying to build in public for future job opportunities) and another self-hosted on Gitea or GitLab for CI/CD.

      That actually sounds like a great setup, so I’ll definitely look into it now. Thanks for the recommendation!