Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

231–240 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#231

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

GitLab is probably a better option for that.

Re: Moving from GitHub to Codeberg, for lazy people

#232
post #176

Earlier quoted context omitted.

Which makes it not really a suitable replacement for GitHub, which is my entire point. Keep in mind, I'm not saying Codeberg is bad , but it's terms of use are pretty clear in the sense that they only really want FOSS and anyone who has something other than FOSS better look elsewhere. GitHub allowed you to basically put up anything that's "yours" and the license wasn't really their concern - that isn't the case with…

(SSG - static site generator) I mean, it is arguably much easier to just write the HTML page and upload it with FTP and everyone can see it. I never understood why github became a popular place to host your site in the first place.

[deleted]

Re: Moving from GitHub to Codeberg, for lazy people

#233
post #178

Everything 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?

> we welcome the world

> maga movement

Re: Moving from GitHub to Codeberg, for lazy people

#234
post #112

The truth is that I publish OSS projects on GitHub because that's where the community is, and the issues/pull requests/discussions are a bonus. If I just want to host my code, I can self host or use an SSH/SFTP server as a git remote, and that's usually what I do.

I have been struggling with this, myself. I used to push everything to GitHub, but a couple months ago I switched over to using my small low-power home server as a Git host. I used to really enjoy the feeling of pushing commits up to GitHub, and that little dopamine rush hasn't really transferred to my home machine yet. It's a shame. The people who control the money successfully committed enshittification against ope…

If you're running forgejo you can setup mirrors [1].

Mine syncs a few repos to github to make them public, and planning to add Codeberg in as well ala POSSE [2].

1. https://forgejo.org/docs/next/user/repo-mirror/

2. https://indieweb.org/POSSE

Re: Moving from GitHub to Codeberg, for lazy people

#235
post #192
post #180

Earlier quoted context omitted.

Because it doesn't require you to run an HTTP server, FTP server, or install an FTP client.

Finding an HTTP+FTP server was easier than finding github. Your OS probably has a FTP client installed already, but finding another one is easier than finding and most definitely easier than learning git. And if you already knew how to write/make HTML you'd for sure already know all of that too.

This is definitely a matter of perspective. I have had a Github account since 2010, and git comes installed on Linux and macOS.

I don't always have a server available to host an HTTP+FTP server on. Or want to pay for one, or spend time setting one up. I can trust that Github Pages will have reasonable uptime, and I won't have to monitor it at all.

> And if you already knew how to write/make HTML you'd for sure already know all of that too.

This seems unnecessarily aggressive, and I don't really understand where it's coming from.

BTW, you can absolutely host plain HTML with Github Pages. No SSG required.

Re: Moving from GitHub to Codeberg, for lazy people

#236
post #55

I'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 went with gitea, but for the same general reasons. I like It has the option to mirror repos up to GitHub for the stuff I actually want to share with the world. Is there anything that made you choose forgejo specifically? I’m not eager to move platforms, but I know there’s more options that have popped up in the years since I first stood up my gitea instance.

Same, Gitea (in Docker) has been running very smoothly for years. Havent had a single issue.

Also now wondering about differences with forgejo.

Re: Moving from GitHub to Codeberg, for lazy people

#237

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

Unfortunately I don't think there's really an answer to that conundrum that doesn't involve just spinning up your own git server and accepting all the operational overhead that comes with it. Hmm all that operational overhead... Of an ssh server? If you literally just want a place to push some code, then that really isn't that hard.

But they don't literally just want a place to push some code. The problem statement included "if GitHub Pages is why you used GitHub".

Re: Moving from GitHub to Codeberg, for lazy people

#238

I don't dislike Codeberg inherently, but it's not a "true" GitHub replacement. It can handle a good chunk of GitHub repositories (namely those for well established FOSS projects looking to have everything a proper capital P project has), but if you're just looking for a generic place to put your code projects that aren't necessarily intended for public release and support (ie. random automation scripts, scraps of con…

FWIW, Pierre's "Code Storage" project [1] seems like it simplifies a lot of the operational overhead of running git servers, if what you want is "an API for git push". Not affiliated with the company (and I haven't tried it myself, so I can't vouch for how well it works), I just think it's a neat idea.

1: https://code.storage/

Re: Moving from GitHub to Codeberg, for lazy people

#239
post #192
post #180

Earlier quoted context omitted.

Because it doesn't require you to run an HTTP server, FTP server, or install an FTP client.

Finding an HTTP+FTP server was easier than finding github. Your OS probably has a FTP client installed already, but finding another one is easier than finding and most definitely easier than learning git. And if you already knew how to write/make HTML you'd for sure already know all of that too.

> And if you already knew how to write/make HTML you'd for sure already know all of that too.

That's a completely false statement. My kid took very basic programming classes in school which covered HTML so they could build webpages, which is a fantastic instant-results method. Hooray, now the class is finished, he wants to put it on the web. Just like millions of other kids who couldn't even spell FTP.

Post reply on HN