Moving from GitHub to Codeberg, for lazy people
181–190 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#182I've been using a self-hosted forgejo (which Codeberg uses and maintains) instance for all of my non-work projects and it's been great. I don't miss GitHub at all. I also keep it accessible only from Tailscale so that AI crawlers and such can speedily make their way into the sun.
I was self hosting gitlab for a long time. But forgejo is an order of magnitude less resource intensive.
It is a single very small go binary. You can use sqlite or postgres. But you can easily run it inside a small docker container on your local machine.
And it is fun to hack on it because it is so open. You build really fun workflows that are blocked by the corporate limits of Github.
Re: Moving from GitHub to Codeberg, for lazy people
#183I think evaluating alternatives to GitHub is going to become increasingly important over the coming years. At the same time, I think these kinds of migrations discount how much GitHub has changed the table stakes/raised the bar for what makes a valuable source forge: it's simply no longer reasonable to BYO CI or accept one that can't natively build for a common set of end-user architectures. This on its own makes me…
I don't understand the hype around CI and that it's supposedly impossible to run something like that without Git, let alone Github. Like sure, a nice interface is fine, but I can do with a simpler one. I don't need a million features, because what is CI (in practice today, not in theory)? It's just a set of commands that run on a remote machine and then the output of those commands is displayed in the browser and it…
Which is actually useful.
Re: Moving from GitHub to Codeberg, for lazy people
#184But that's the most important part. A repository without CI is basically dead.
The biggest challenge of this era is automated verification, and proper CI infrastructure is essential.
GitHub feels like what Hudson/Jenkins was some decades ago. Horrible, but the only one that did what it did.
I run probably hundreds of dollars of CI on GitHub per month. Except I don't pay a cent for it (all open source public repos). I can't just let that go, those workers do real work.
Re: Moving from GitHub to Codeberg, for lazy people
#185Everything runs on servers that we control. We will not sell your data. Hosted in Europe, we welcome the world. ``````` so it's you control, make money vs they control make money. what is the difference here , except some eu version of maga movement here?
Re: Moving from GitHub to Codeberg, for lazy people
#186Earlier quoted context omitted.
Anyone actually scraping git repos would probably just do a 'git clone'. Crawling git hosts is extremely expensive, as git servers have always been inadvertent crawler traps. They generate a URL for every version of every file on every commit and every branch and tag, and if that wasn't enough, n(n+1)/2 git diffs for every file on every commit it has exited on. Even a relatively small git repo with a few hundred file…
How probable is your "probably"?
Re: Moving from GitHub to Codeberg, for lazy people
#187Earlier quoted context omitted.
> I publish OSS projects on GitHub because that's where the community is And so we go, forever in circles, until enough of us move to other platforms regardless of where the existing community is. Just like how GitHub found its community in the early days, when most people (afaik) was using SourceForge, if anything. "The community" will always remain on GitHub, if everyone just upload code to where "the community" al…
> "The community" will always remain on GitHub, if everyone just upload code to where "the community" already is. If enough of us stop using GitHub by default, and instead use something else, eventually "the community" will be there too, but it is somewhat of a chicken-and-egg problem, I admit. SourceForge was abandoned due to UX issues and the adware debacle; at the same time, GitHub started making changes which mad…
People have a superficial knowledge of the space (I think this extends beyond Codeberg) but feel strongly that they need to advocate for something. Codeberg themselves seem to have opinions about what they want to do but people are suggesting they can do more simply because it gives them an outlet.
The constraints that Codeberg set seem to, on the surface at least, ensure they can scale based on their needs and protect them from external threats. Hosting random sites comes with a range of liabilities they probably understand and want to avoid right now. There are EU regulations which can be challenging to handle.
Re: Moving from GitHub to Codeberg, for lazy people
#188Earlier quoted context omitted.
From their FAQ: > If you do not contribute to free/libre software (or if it is limited to your personal homepage) , and we feel like you only abuse Codeberg for storing your commercial projects or media backups, we might get unhappy about that. Emphasis mine. This isn't about if it's technically possible (it certainly is), it's whether or not it's allowed by their platform policies. Their page publishing feature seem…
That FAQ snippet is insane to me. Maybe it's a cultural thing but I'd never do business with a company that has implicit threats in their ToS based on something so completely arbitrary.
Re: Moving from GitHub to Codeberg, for lazy people
#189Everything runs on servers that we control. We will not sell your data. Hosted in Europe, we welcome the world. ``````` so it's you control, make money vs they control make money. what is the difference here , except some eu version of maga movement here?
Codeberg is just a hosted instance of Forgejo (GPLv3).
They even support a workflow for migrating to a different Forgejo instance [1].
Re: Moving from GitHub to Codeberg, for lazy people
#190Earlier quoted context omitted.
From their FAQ: > If you do not contribute to free/libre software (or if it is limited to your personal homepage) , and we feel like you only abuse Codeberg for storing your commercial projects or media backups, we might get unhappy about that. Emphasis mine. This isn't about if it's technically possible (it certainly is), it's whether or not it's allowed by their platform policies. Their page publishing feature seem…
Seems fair to me, they're a nonprofit that exists in our lived reality and not an abusive monopolist that can literally throw a billion dollars to subsidize loss leaders. All it shows the world is why there needs to be a VAT like tax against US digital services to help drive a public option for developers. There's no reason why the people can't make our own solutions rather than be confined to abusive private US tech…
A better alternative would be to create the incentives so that companies like these can be born in Europe.