Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

341–350 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#341

Earlier quoted context omitted.

Nonprofit, not a company. as far as I can tell they don’t accept payment for anything so they don’t want your “business”.

Which is why they are not a Github replacement for everyone.

They're a perfectly fine replacement if you care about FOSS and OSS, unlikely github + msft.

Re: Moving from GitHub to Codeberg, for lazy people

#342

Earlier quoted context omitted.

I think both of you are misunderstanding what I proposed. You just need a single VM with an ssh server. Literally no web service needed, if all you want to do is host some code remotely.

VM and ssh. Needs linux admin exp. Security updates. Understand how to securely connect from an IP without opening 22 on 0.0.0.0/0

Opening ssh to the internet is fine if you are using key based auth, which is the default on many VM setups.

Re: Moving from GitHub to Codeberg, for lazy people

#343

Earlier quoted context omitted.

ssh isn't a web service (some would argue that smtp and ftp aren't too as they came before the web). And I believe GP was talking about the only thing you need is: ssh user@remotehost git init --bare repo.git And then you can add the remote to your local repo with git remote add origin user@remotehost:repo.git Now all you need to do is git push origin branch_name Replace origin with another identifier if it's already…

The rest of the owl: go to provider, set up VM (20 questions) log into root. SSH for login. set up firewalls. create non-root user. useradd or adduser? depends if you want a home dir I guess. debug why you can't ssh in. Finally get in. sudo apt update. sudo apt install git (or is it named something else?). install failtoban. install fw. then do above. then troubleshoot. set vm backup policy. save myriad passwords and…

I could write a much more complicated list of steps for github.

Re: Moving from GitHub to Codeberg, for lazy people

#344
post #151

What I'd like to see is a lazy person's HOWTO for the last paragraph: > You could tell Codeberg to push new commits to GitHub, but this allows users to still file PRs and comment on issues and commits 2. Some folks have dealt with this by disabling issues on the GitHub repo, but that is a really destructive action as it will 404 all issues, and pull requests cannot be disabled. Some repos like libvirt/libvirt have wr…

Disabling PRs is now possible on GitHub: https://github.blog/changelog/2026-02-13-new-repository-sett... You can limit them to contributors as well.

Thanks. Doesn't seem to be supported by `gh` yet.

Re: Moving from GitHub to Codeberg, for lazy people

#345

Earlier quoted context omitted.

> and use robots.txt as a guide of what to crawl rather than what not to crawl Mental note, make sure my robots.txt files contain a few references to slowly returning pages full of almost nonsense that link back to each other endlessly… Not complete nonsense, that would be reasonably easy to detect and ignore. Perhaps repeats of your other content with every 5th word swapped with a random one from elsewhere in the co…

This is one reason why most crawlers ignore robots.txt now. The other reason is that bandwidth/bots are cheap enough now that they don't need web admins to help them optimize their crawlers

> This is one reason why most crawlers ignore robots.txt now.

I don't buy that for a second. Those not obeying robots.txt were doing so either because they were malicious (they wanted everything and wouldn't be told “please don't plough through these bits”) or stupid (not knowing any better) or both.

Anyone who was obeying robots.txt isn't going to start ignoring it because we've put honeypots there. Why would they think “well, now there are honeypots there I'm going to go scan those… honypots, yeah, that's a good idea”.

> The other reason is that bandwidth/bots are cheap enough now that they don't need web admins to help them optimize their crawlers

Web admins are not trying to optimize their crawlers, they are trying to stop their crawlers breaking sites.

Re: Moving from GitHub to Codeberg, for lazy people

#346

I don’t know what everyone else thinks, but for me, GitHub is a shining star among most developer tools and services. Free hosting for code, sites, personal projects, no obligation to make your repositories public or buy a subscription. For most devs, they would never need to buy a subscription. Heck, I don’t need it, but I pay for it as a thank you for what I get (have gotten) out of it. I am honestly shocked that t…

Thrive? No. GH has been getting very noticeably worse. The uptime is terrible now and the UI is a lot flakier.

So their usage has shot up post AI agents/agentic coding. We are seeing the effects via their struggle to keep up with demand. That by itself does not make the service bad. Claude did not even make it to two nines for January (98.9% availability).

Source: https://bsky.app/profile/teropa.bsky.social/post/3mi2dbt27m2...

Re: Moving from GitHub to Codeberg, for lazy people

#347
post #156

Earlier quoted context omitted.

Considering that "the community" is now filled with vibe coding slop pull requesters, and non-coders bitching in issues, the filter that not-github provides becomes better and better. Of course, that mostly goes for projects big enough to already have an indepedent community.

Not to contradict you, but there's another important aspect to 'community' besides the bad contributors and the entitled complainers. That's discoverability. How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Searching each one individually is not a viable proposition. The search often ends on the biggest platform - Github. I'm not trying defend github here. The l…

I don't think I ever find new software through github's own search. I find them through the software's website or some other means like a search engine.

Re: Moving from GitHub to Codeberg, for lazy people

#348
post #281

Earlier quoted context omitted.

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…

I find CI very valuable even on my solo projects. > 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 also influences what other commands may or may not run. What exactly is the big deal here? The key is hermetically/reproducibly - you don't want to run commands on some random machine, you wa…

These days the reproducibility part is trivial with a Docker container, as much as it's a mess of a technology.

Re: Moving from GitHub to Codeberg, for lazy people

#349

Earlier quoted context omitted.

My reading is: Don't attempt to store your media (photos, music, videos, etc.) collection there, and you won't have any issues.

I don't like how it reads differently based on perspectives, they should be crystal clear on what's allowed and what's not, but when they say '...unhappy about...' as a statement, it feels kinda amateur to me although I'm pretty sure the operators must be way capable than me lol.

Totally agreed. I get the feeling they have not yet had to draw too many lines in the sand... Yet. So they're probably keeping it flexible until they have to really start swinging the hammer.

Re: Moving from GitHub to Codeberg, for lazy people

#350

Earlier quoted context omitted.

Thrive? No. GH has been getting very noticeably worse. The uptime is terrible now and the UI is a lot flakier.

So their usage has shot up post AI agents/agentic coding. We are seeing the effects via their struggle to keep up with demand. That by itself does not make the service bad. Claude did not even make it to two nines for January (98.9% availability). Source: https://bsky.app/profile/teropa.bsky.social/post/3mi2dbt27m2...

I mean, I don't know anything about Claude. That sounds like it could be normal for a heavily vibe-coded project.

But GH was pretty stable for a decade or so, through many changes. I don't think there's that much new activity. The UI bugginess is also new.

Post reply on HN