[herpdyderp]

Right? I was seriously considering migrating everything in our company from GitHub to GitLab. Now I'm seriously considering self hosting our git instead.

[hkpack]

Self-host your git, take this as a sign.

Forgejo is great.

[thayne]

There are a lot of downsides to self-hosting your git as well. Especially if you need to deal with high availability, scalability beyond a single server, and/or being open to the public Internet.

I'm not saying you should never self-host your git server, but it's not for everyone.

[phoronixrly]

Good thing Github suck at availability and scalability much more than your friendly local sysadmin...

[shimman]

No, these things are actually much easier to solve when you don't have to care for millions of users across every timezone and can just focus on <10,000 users that can easily be handled with a modest VPS setup.

It's truly pathetic how developers today cede everything to cloud services. A $20 VPS (whatever gets you 4 gigs of ram) is likely enough to host all the business needs of 90% of SMBs across the US.

Even easier today with things like Docker, Forgejo, and other great self hosting solutions.

Why would a company care about opening up their codebase to the internet? These are problems you don't have to care about when you only want a small subset of solutions. Especially when the tradeoffs are drastically simpler.

[com]

These days even without trying I get more nine than GitHub.

Arguments against self hosting have to change as our SaaS overlords are decaying in front of our very eyes.

[Balinares]

Forgejo is fantastic! Just wish there was an easier way to implement CI/CD pipeline runners.

[abalashov]

You'd be surprised how far you can get with self-hosted Gitea.

[abnercoimbre]

Can highly recommend it. Gitea issues, PRs and actions all work as expected.

[SV_BubbleTime]

My bar for self-hosting something isn’t “these base standard feature works”, they had fucking better.

I get self-hosting got for security, compliance, and retention reasons, but for almost everything else it seems questionable for any use I would consider normal.

[abalashov]

I self-host because I'm not training some model for free with our and our customers' proprietary code.

[abalashov]

And they have a suspiciously well-appointed MCP server.

[phillipcarter]

Using Tangled for my stuff now, it's alpha, but it's a bit fun to host your own Knot and Spindle servers but still connect to a full social graph.

[akshitgaur2005]

Its VC funded too, so I wouldn't bet too much on it. Try out ngit or radicle, or codeberg if your code is open-source

[phillipcarter]

It's also entirely OSS. Codeberg's nonprofit could crater in the near-term, too.

[daemin]

I don't think hosting git is all that complicated, just install it on a server, create a repo, and push to it.

What is complicated is having a convenient interface for managing the repository (users, groups, and hook-actions) and showing what the repository contains (commits, branches, tags).

I remember back in the day the first part was handled adequately with software like gitosis and gitolite, which just used git repository to manage other git repositories on the system.

[youre-wrong3]

I find these takes funny. One day you will leave or get let go and someone will be like “finally we can move to a proper system”

[phoronixrly]

Times change, maybe at this point there will be a 'proper system'. Unlike Github and GitLab now...

[Ekaros]

I just look at the pricing and really start thinking about is it really multi hundred euro a year per seat product... Frankly as consumer those pricing levels just seems like distanced from reality.

[walrus01]

I don't know if that really solves your problem if the main trunk of development for gitlab is being run through several AI slop machines before they push it to what they call stable, then you download that (or use a debian, redhat package for gitlab which originated from it) and self host on your own machine the results of the AI slop fest.

[thfuran]

There are other forges.