Re:Another GitHub outage in the same day
by Kovah on Monday February 09, 2026 @03:10PM
(#46950468)
I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works. Any good recommendations?
[ Parent
| on HN ]
Re:Another GitHub outage in the same day
by adamcharnock on Monday February 09, 2026 @03:33PM
(#46950812)
We can run a Forgejo instance for you with Firecracker VM runners on bare metal. We can also support it and provide an SLA. We're running it internally and it is very solid. We're running the runners on bare metal, with a whole lot of large CI/CD jobs (mostly Rust compilation).
The down side is that the starting price is kinda high, so the math probably only works out if you also have a number of other workloads to run on the same cluster. Or if you need to run a really huge Forgejo server!
I suspect my comment history will provide the best details and overview of what we do. We'll be offering the Firecracker runner back to the Forgejo community very soon in any case.
You've got any docs for firecracker as forgejo runners?
Re:Another GitHub outage in the same day
by adamcharnock on Tuesday February 10, 2026 @05:28AM
(#46957770)
Ping me an email, adam@ domain.
If you're interested I'll see about getting the PR created sooner rather than later.
I actually went through some of the issue/pr stuff for the forgejo project after I asked you. It seems like things are moving along nicely and you seem to have found a welcoming environment in their repo. I will keep an eye on that progress. Thanks very much. I do not have a pressing need but firecracker runners would be pretty awesome to have.
Re:Another GitHub outage in the same day
by adamcharnock on Monday February 16, 2026 @10:41AM
(#47036399)
FYI, PR created: https://code.forgejo.org/forgejo/runner/pulls/1382
Awesome. Thank you for letting me know and good luck with the PR!
Re:Another GitHub outage in the same day
by joeskyyy on Monday February 09, 2026 @03:20PM
(#46950608)
Long time GitLab fan myself. The platform itself is quite solid, and GitLab CI is extremely straightforward but allows for a lot of complexity if you need it. They have registries as well, though admittedly the permission stuff around them is a bit wonky. But it definitely works and integrates nicely when you use everything all in one!
Re:Another GitHub outage in the same day
by dylan604 on Monday February 09, 2026 @03:20PM
(#46950623)
Should our repos be responsible for CI in the first place? Seems like we keep losing the idea of simple tools to do specific jobs well (unix-like) and keep growing tools to be larger while attempting to do more things much less well (microsoft-like).
I think most large platforms eventually split the tools out because you indeed can get MUCH better CI/CD, ticket management, documentation, etc from dedicated platforms for each. However when you're just starting out the cognitive overhead and cost of signing up and connecting multiple services is a lot higher than using all the tools bundled (initially for free) with your repo.
Why this and not Garnix?
Lots of dedicated CI/CD out there that works well. CircleCI has worked for me
Re:Another GitHub outage in the same day
by cyanydeez on Monday February 09, 2026 @03:25PM
(#46950697)
GitLab can be selfhosted with container based CI and fairly easy to setup CE
Re:Another GitHub outage in the same day
by IshKebab on Monday February 09, 2026 @03:34PM
(#46950817)
CE is pretty good. The things that you will miss that made us eventually pay:
* Mandatory code reviews
* Merge queue (merge train)
If you don't need those it's good.
Also it's written in Ruby so if you think you'll ever want to understand or modify the code then look elsewhere (probably Forgejo).
GitLab, best ci i’ve ever used.
Gitea / forgejo. It supports GitHub actions.
Re:Another GitHub outage in the same day
by yoyohello13 on Monday February 09, 2026 @06:22PM
(#46953037)
GitLab has all the things.