hey nerds! i got a lovely email from GitHub this morning that their increasingly vibe-coded, barely-working Actions features are about to get more expensive (charging by the minute for something that notoriously spin-locks is a special flavor of shit sandwich).

i usually just use whatever i’m given at wherever i’m working. i do have a project that i maintain to parse Ollama Modelfiles tho: https://github.com/covercash2/modelfile and to be honest, Actions is the only solution i’ve ever used that came close to sparking joy, simply because it was easy to use and had tons of community mind-share (i’ve definitely heard horror stories and would never stake my business on it), but this price increase and all the other news around GitHub lately has got me side-eying self-hosting solutions for my git projects. Forgejo seems like the way to go for git hosting, but Actions in particular Just Works™️ for me, so i’m kind of dreading setting something up that will be yet another time sink/rabbit hole (just in time for the holidays! 🙃).

i can install most of my tooling with my language toolchain (read: rustup and cargo) which makes things fairly neat, but i just don’t have a sense for what people use outside of Jenkins and Actions.

i thought this community might have some insight beyond the LLM generated listicles that have blighted modern search results.

thanks in advance 🙏

  • Carol2852@discuss.tchncs.deEnglish
    13·
    23 hours ago

    I’m using gitea which has CI compatible to GitHub actions with my own runner. It’s pretty straightforward to set up and didn’t give me any headaches yet. It’s a very small instance just for my ownaybe dozen projects though.

    • yaroto98@lemmy.worldEnglish
      6·
      23 hours ago

      This is what I was using till I switched to forgejo and never got around to setting up one of their runners.

      • Carol2852@discuss.tchncs.deEnglish
        2·
        12 hours ago

        I run their act binary on one of my servers. Can’t remember much of the setup, so I can’t be too bad. I did have to change the used images though, but I guess that comes with maintenance of you own runner anyway.

      • witten@lemmy.worldEnglish
        1·
        12 hours ago

        Out of curiosity, how did you switch to Forgejo? I thought Gitea and Forgejo have diverged to the point where you can no longer just switch over without losing stuff.

        • yaroto98@lemmy.worldEnglish
          1·
          4 hours ago

          I hadn’t used gitea for long. I just had both running, and then cloned my repos one at a time manually. So long as I had the code, I didn’t really care.

      • Finn@toot.fan
        1·
        12 hours ago

        @yaroto98 @Carol2852 Same here, switched from gitea to forgejo. I still was using the act runner for some time, later I replaced it with the forgejo-runner.

        Works pretty smooth!

      • cecilkorik@lemmy.caEnglish
        2·
        21 hours ago

        If it helps motivate you to give it a shot, I found gitea’s runner very confusing to set up, but I felt like forgejo was better designed, pretty easy and well documented.

    • chrash0@lemmy.worldOPEnglish
      2·
      23 hours ago

      good lead. it’s just the one project for now, and to my surprise it’s actually a dependency for the ollama-rs project, so i feel somewhat obligated to keep it stable.