[bigfatfrock]

Who's going to kick off the holy war around self hosting?

[reddalo]

Speaking of self hosting, Codeberg [1] is great. It's open and it looks and behaves pretty much like GitHub (unlike GitLab).

[1] https://codeberg.org/

[diggan]

Seconded. Hosting FOSS on a platform that isn't FOSS itself and run by a for-profit company who tried to work against FOSS for so long (Microsoft) doesn't make much sense to me.

Instead, we should dogfood the FOSS ecosystem on a platform that is FOSS itself, and run as a non-profit. Codeberg, for better or worse, is the best platform for this today.

[mr_mitm]

Did you mean to say Forgejo? Correct me if I'm wrong, but Codeberg is simply hosting a Forgejo instance for you, so not exactly self hosting.

[otter-in-a-suit]

Since you asked, https://about.gitea.com/ is a great tool. MIT license.

[NewJazz]

Would be even better if they didn't require a CLA to contribute.

[skydhash]

Personal projects are on a vps and accessed through ssh. I’ve self-hosted gitea, then forgejo, then found out that I don’t like the interface or the auth dance. My plan is to ise cgit if I want something to be public and any forge if the purpose is collaboration (sourcehut is nice)

[duxup]

Honestly, sounds like a lot of work and I'm not sure I get much benefit, or even less downtime.

I don't know about others but for me github is hardly a service that I'm sweating moment to moment uptime. My apps are still running and so on.

[cropcirclbureau]

Hosting GitLab is not fun but anyways, M$ can still suck it.

[zaruvi]

Not Onedev or Forgejo, though it could get tricky depending on what features you require.

[rvz]

It all began 5 years ago [0] when we wanted to 'centralize everything to GitHub.'

Then, the outages accelerated from there.

[0] https://news.ycombinator.com/item?id=22868406

[mrguyorama]

"are you sure your self-hosted solution will have better uptime?"

Hilariously, after 15 years working in self hosted bitbucket systems, YES entirely.

An underfunded university with an incompetent but doing their best IT department? Zero downtime.

A mid sized company full of overly confident and "just build it" nerds building fragile shit? Zero downtime.

A large corporation with a completely outsourced IT department that can't give you access to something unless you do exactly the right undocumented thing in our internal ticketing software? Zero downtime.

That includes self hosted jenkins and literally homebuilt infrastructure with zero documentation and the guy that built it left a while ago.

I have never been able to blame our build and code infra for lack of productivity.