Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Forgejo is great to self host. I have an easy to use template for setting it up on fly.io with backups here: https://forgejo-fly.fly.dev/forgejo-admin/forgejo-flyby ryuuseijin
- Forgejo is splendid. Codeberg is a hosted instance; depending on what you’re developing it may or may not be a good fit for you. But the Forgejo stack itself is decently light-weight to self-host, very fast to use, and is easy to navigate.by ashton314
- Codefloe[1] is another forjego (with some custom patches, I believe) hosted instance.
[1]: https://codefloe.com
- > depending on what you’re developing it may or may not be a good fit for you
I think if your project is free / open source (edit: and you don’t use LLMs/AI), Codeberg is the a good starting point at least. You can move on to a self-hosted instance if you feel you’ve outgrown it, but even for larger projects I think you can get away with self-hosting just the CI runners.
And don’t forget to donate! https://donate.codeberg.org/ / https://join.codeberg.org/
by notpushkin - I've used gitlab and gitea; gitea is faster, and easier to manage and does everything I actually need though, is less feature complete.by ukd1
- I tried Gitea for a while but the support mechanism was "Beg for help on Discord and hope someone replies", this left us high and dry a few times.by scientifik
- I'm one of the project leads of Gitea. I'd be interested in knowing which features you are missing from Gitea compared to Gitlab? We are doing some backlog grooming right now, and input is very appreciated:)
- I'm screwed because I am part of an ecosystem that all lives in github.
I'm not happy about the fact that GH doesn't show my when new issues or PRs are filed against projects I maintain despite the notification settings implying I should be getting notifications, but at least it's not Atlassian.
I was working on major architecture shifts for a couple of libraries, to fix early mistakes or improve performance. I noticed that of them used a tool A that was dead, built on another tool B that was even deader.
I found someone who was building a new B, and I made a new A and offered to swap in it on the one project. That went well, so then I integrated it to the other projects I was contributing to. Which I'm now also a maintainer on.
And also the 'new B', because I pushed the intent of his library farther than he had been thinking about, contributing about 20% of the public facing API and about 5% of the internals.
One of those projects is a monster, of which I'm just on a subproject. I'd never be able to get them all to move off. And any mix of GitHub and ^GitHub results in the amount of busy work I have to do to keep on top of issues and PRs more than doubles.
And that's how the getcha.
by hinkley - by quaintdev
- How easy is it to set up and run this for private repos?
It looks like it has so many cool features -- stacked PRs, jujutsu support, CI in Nix VMs. But I've never tried it because it sounds like (at least by default) it's some sort of decentralized, peer-to-peer public thing
by ch71r22 - First I've heard of this, but they seem to be a young, smart and energetic team on a great trajectory. The atproto choice is interesting, fits their social-minded goal.by izolate
- I strongly disagree with the assumption that GitHub's alternative is another centralized forge. Git itself is perfectly decentralized, as was the original Linux kernel development process. How people managed to put all their eggs in one intermittently available service is beyond me. Moving the eggs into another bucket is not a solution (like Microsoft is short of servers). The SPoF is the problem. There are plumbing, porcelain and "github" layers. The "github" part has to be decentralized as well. Then, using a particular forge will be a choice of convenience, not necessity. https://replicated.live/blog/crdtby gritzko
- > How people managed to put all their eggs in one intermittently available service is beyond me.
It's beyond me how people on HN can be ignorant to why GitHub gained so much market share. It's because for most dev teams, the things they add to the easily decentralized git core is *very valuable.* Arguing it's not valuable or ignoring that value doesn't help anyone.
If decentralized is really going to win, then you have to have the features and DevX to match the basics GitHub provides. Because that's what people need/want. And not just the candy-ass-not-as-good-as-the-kernel-devs devs. Lots of very talented people and very well engineered projects use GitHub because it's better for what they need. Even with all the outages, people are still there. If it was so easy to move away, people would. The fact that they aren't says something important. Please consider not ignoring it.
by rsyring - Oh, it’s really simple why this happened:
1. People do not like email-based patch processes.
2. GitHub made everything dead simple, and free. Lots of Open Source projects have flourished because GitHub is both easy to use and makes collaboration across repository painless.
3. Very few people actually care about decentralization. As long as you have a full copy of your repo on your own machines as well as GH, it’s hard to argue you’re gaining anything with decentralization.
4. Most people also don’t want to self host a git server.
by anon7000 - I migrated everything to codeberg several months ago (and created an annual donation schedule). I was never a big fan of github but what ultimately pushed me to ditch it was the way github was shoving copilot/chatgpt in my face without me ever asking. Codeberg has a clear stance on that and it's a stance I can totally get behind.
In addition I spun up forgejo at a server at home for very critical stuff and it's awesome.
by axegon_ - Codeberg for open source and Forgejo for private (and slop, if you're into that kind of thing) is what winners doby bogwog
- Note: If you use any form of AI-assisted coding tools, your project breaks Codeberg TOSby babelfish
- Note: if your reason for switching is purely uptime, you will be sorely disappointed with codeberg
Their own site reports the 2 week uptime at 1 nine https://status.codeberg.org/status/codeberg and I suspect if you use the (really terrible) across-all-product-offerings uptime methodology that people love to post for github it would be a 0 nines overall service.
by Anon1096 - I answered this in another thread, if you're already running a large GitHub organization, GitLab is the closest alternative in terms of features
A big plus is that it also has an open-source Community Edition that you can self-host
by mariocesar - There are also many consultancies able to provide professional support with running it in your org, including migrations.by Nemo_bis
- by polycaster
- Is their CI and CD workflow robust like gitlab/github ?by bobkb
- I recently set this up on my homelab, not really expecting to switch to it, more out of interest. But wow, after I saw how unbelievably fast it was, I’ve moved everything over. I’ve now set it up to mirror things automatically to Github if I want to make them public.
Using Github at work is painful in comparison. (Also literally just this morning we’ve had to delay a release due to Github being down.)
by sandcat_ - https://tangled.org! Founder/CEO here. We're a new forge building things from the ground up, and are fully federated -- you can host your git repos on your own infra, along with the CI runners. We've also got a pretty neat set of features (if I may say so myself): stacked PRs, Nix-based CI (if you want it), and a fully open protocol (https://atproto.com) to for you and your agents.
Happy to answer any questions.
by icy - I wanted to use tangled but my repo is SHA256 and you sadly don’t support it. I know SHA256 is not very usual but anyway, do you plan to support it?by rebolek
- The "social media" platform aspect is really offputting. That's really one of the aspects where it's obvious that GitHub lost perspective of its purpose.
And atproto isn't really something I'd want to be around; it's really associated with the wrong crowds.
by WhyNotHugo - I think the main thing I'm waiting for in the atproto space, for _most_ applications, is private data solutions. And the recent RFC on private data spaces (I forget the terminology) is a start, but has a ways to go.by eximius
- Just signed up, so not much to report yet, but one thing I noticed is that, because the sign in is on tngl.sh rather than a subdomain of tangled.org, it might be confusing for some users, especially as the sign in page has a very different design, theme and layout to the rest of your website and tangled as a whole. Additionally, my password manager didn't show the just created password due to the URL mismatch. Perhaps this could be addressed to improve the experience.
Edit: I really like that one-click "watch logs via SSH" copy button. Maybe those could be attached to the top of the top, as it stands the pipeline just pushes them further and further down. Find the UI and UX overall very pleasant.
by Topfi - Tangled feels like the future but it seriously needs private repos ASAP to capture the momentum of the current GitHub exodus.by jkl5xx
- I recently got a spindle and a knot set up on my home server (along with Tranquil PDS). A few rough edges that we got ironed out but it's cool to have all of that self-hosted on my own machine yet still part of the AT proto world! I'll be honest, I'm not putting anything critical on it yet but that's my lack of trust in my own home server setup not doubt in Tangled's infra!
A better web UI for the queued jobs on my spindle would be great btw!
by MerrimanInd