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

  • ikidd@lemmy.worldEnglish
    4·
    5 days ago

    I like that. I tried to get Actions in Forgejo working and that was a dead-end. So I’ve been using act manually.

    Appreciate the writeup.

      • ikidd@lemmy.worldEnglish
        1·
        4 days ago

        actions/setup-java@v4 would fail trying to find the java setup script at Forgejo’s runner source repo, and apparently it wasn’t there when I went to look. I’ll look at it another time when maybe all the backend is put together or there’s a way I can host the actions locally so I’m not relying on outside sources that might pollute my CI output.

        • arcayne@lemmy.todayEnglish
          1·
          3 days ago

          With both Gitea and Forgejo, sometimes you need to hardcode the action URL, like:

          https://github.com/actions/setup-java@v4
          • ikidd@lemmy.worldEnglish
            1·
            3 days ago

            I followed where it was going and it was a forgejo repo where there were some action sets but not that one. I figured they were using their own sets and hadn’t gotten around to java yet.

            • arcayne@lemmy.todayEnglish
              1·
              3 days ago

              Well, yeah, thats why I’m saying if the action isn’t available directly from Forgejo, just write out the full action URL like the example in my last comment and pull it directly from GitHub. Most/all of the actions you’re pulling from Forgejo are originally forked from GitHub anyway. ¯\_(ツ)_/¯