> is $0.002/minute a good price for this

Absolutely not, since it's the same price as their cheapest hosted option. If all they're doing is orchestration, why the hell are they charging per-minute instead of per-action or some other measure that recognizes the difference in their cost between self-hosted and github-hosted?

Have any suggestions to those community-developed and maintained options?

Gitea. Gitlab (ish?).

GitLab actually implemented Actions first back in the day (called CI/CD). I remember GitHub was following their lead.

Which is funny reading how TFA tries to feign ignorance:

> When we shipped Actions in 2018, we had no idea how popular it would become.

Gitea scales really badly with large repos in my experience. Gitlab works a lot better mostly because you can just throw more hardware at it. This is with a pretty large git repo and a lot of daily commits.

On the other hand, gitlab is a memory hog. You need a big vm dedicated to it.

We were on codeberg for a couple years and it was fine.

Yeah Gitlab is a pig, but that’s what I meant with you can throw hardware at the problem. I’ve been meaning to check out Codeberg for personal project hosting since it seems to address the shortcomings of gitea

GitLab scales much better horizontally than it does vertically.

4x 4c/16gb instances will perform much better than one 16 core 64GB instance.

You can also just use Gitlab Cloud but setup as many self hosted runners as you like.

>Gitea scales really badly with large repos in my experience.

Isn't it written in this super scaling language that everybody says scales super well?

What is the problem with it?

I can't decide if this article is satire.

I was asked to click "continue" after each of the first two sentences, and the fade-in of the text took longer than reading the text.

This may be a great article, but I'll never know because it's frustrating to try and read.

This concept has been around for ages. I remember way back in a previous life as a Java dev having a framework where you could annotate methods with permission requirements, and the framework would add runtime instrumentation to ensure the proper context was created in the current thread and had the proper permissions to invoke that method any time it was called.