Self-host your git, take this as a sign.
replyForgejo is great.
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.
replyI'm not saying you should never self-host your git server, but it's not for everyone.
Good thing Github suck at availability and scalability much more than your friendly local sysadmin...
replyThese days even without trying I get more nine than GitHub.
replyArguments against self hosting have to change as our SaaS overlords are decaying in front of our very eyes.
[dead]
replyForgejo is fantastic! Just wish there was an easier way to implement CI/CD pipeline runners.
replydeleted
replyYou'd be surprised how far you can get with self-hosted Gitea.
replyCan highly recommend it. Gitea issues, PRs and actions all work as expected.
replyAnd they have a suspiciously well-appointed MCP server.
replyMy bar for self-hosting something isn’t “these base standard feature works”, they had fucking better.
replyI 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.
I self-host because I'm not training some model for free with our and our customers' proprietary code.
replyUsing 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.
replyIts 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
replyI 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”
replyTimes change, maybe at this point there will be a 'proper system'. Unlike Github and GitLab now...
replyI 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.
replyI 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.
replyThere are other forges.
reply[flagged]
replyClickbait titled "Microsoft doesn't want you to know this"
replyWow people do not know that?
reply