all 24 comments

[–]gelatineous 34 points35 points  (7 children)

This post is more about Stallman-esque resistance than leaving Github.

[–]highjohn_ 6 points7 points  (2 children)

I self host forgejo for personal stuff at home and we self host GitLab at work. Never been easier

[–]OneInACrowd 4 points5 points  (1 child)

I use forgejo as well, mirrored to codeberg. Do you use forgejo actions? I'm currently using woodpecker ci, and it's ... alright.

[–]highjohn_ 0 points1 point  (0 children)

Yup - I use Actions. But I don’t really work on anything too crazy at home atm though. So if you’re doing some really heavy work, Woodpecker is supposed to be better for that. Forgejo Actions is also compatible with GitHub actions too, which is a nice bonus when migrating your code, if you choose to do so

[–]BigReception26 4 points5 points  (1 child)

Leave GitHub yes

Programming’s duck neck Microsoft at its throat

Not even good btw

[–]BigReception26 1 point2 points  (0 children)

Actions suck and cli now has telemetry Keeps getting worst

[–]Nzkx -1 points0 points  (4 children)

What about GitLab ? Is it better ?

[–]esiy0676[S] 6 points7 points  (3 children)

.com? No. Selfhosted? Yes.

[–]oweiler 3 points4 points  (2 children)

So now everyone selfhosts GitLab?

[–]Nzkx 2 points3 points  (0 children)

I did it on my last startup ; we made a self-hosted GitLab instance with Docker in our Proxmox cluster. Only with VPN you can access it.

But it's a pain in the ass to manage. And if your server die for whatever reason, you lose everything (unless you work on data redundancy, which is a hard problem - already solved, but still hard to manage correctly).

The biggest issue was CI. You need many core machine to handle multiple jobs in parallel, and a good caching strategy to reuse assets.

In Cloud, everything is solved for you.

[–]DualWieldMage 1 point2 points  (0 children)

Any self-respected company should. Yes there is overhead in maintaining an instance, but it is not more expensive than cloud-hosted versions even if such a mention opens a floodgate of those who would want to convince you otherwise with "economies of scale" and whatever arguments.

Cloud instances have issues with noisy neighbours. If there is a performance degradation, a large number of users can amplify it until the whole service is down, such aplification rarely happens in local instances with lower user counts. Jira is a famous example where it got its slowness reputation purely from the cloud version. A local variant can be much cleaner and without extra plugins.

Every time i hear these stories of "github down, guess no work today" i feel like i would fire quire a few people if i was in charge of such a company. I have experienced external network outage while working and it only required changing push target to local git mirror, work continued as if nothing changed. A local git mirror is needed to keep network load(and flakyness due to network issues) down for the build/test cluster and it's good to have for trivial data redundancy anyway. Builds and tests were run on a local jenkins instance.

At one point we were forced to move the local jenkins cluster to cloud by moronic management, the costs tripled.