Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

51–60 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#51

I 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…

> it's simply no longer reasonable to BYO CI Why? I know plenty of teams which are fine with repo and CI being separate tools as long as there is integration between the 2.

Emphasis on teams; the median open source project has a fraction of a single person working on it.

Re: Moving from GitHub to Codeberg, for lazy people

#53

Earlier quoted context omitted.

For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…

> If that gets interrupted, then I have resort to things like rsyncing over from the other system I'm guessing you have SSH access between the two? You could just add it as another remote, via SSH, so you can push/pull directly between the two. This is what I do on my home network to sync configs and other things between various machines and OSes, just do `git remote add other-host git+ssh://user@10.55/~/the-repo-pat…

Usually one of two things, mostly the latter: I forget to exclude all the .git/ directory from the sync, or I have in-progress and nowhere near ready for commit changes on both hosts, and I forget and sync before I check. These are all PEBKAC problems and/or workflow problems, but on a typical day I'll be working in or around a half-dozen repos and it's too easy to forget. The normal git workflow protects from that because uncommitted changes in one can just be rebased easily the next time I'm working in that on any given computer. I've been doing it like this for nearly 20 years and it's never been an issue because remotes were always quite stable/reliable. I really just need to change my worfklow for the new reality, but old habits die hard.

Re: Moving from GitHub to Codeberg, for lazy people

#54
post #5

Lazy has nothing to do with it, codeberg simply doesn't work. Most of my friends who use codeberg are staunch cloudflare-opponents, but cloudflare is what keeps Gitlab alive. Fact of life is that they're being attacked non-stop, and need some sort of DDoS filter. Codeberg has that anubis thing now I guess? But they still have downtime, and the worst thing ever for me as a developer is having the urge to code and not…

[flagged]

Thanks for your input

Re: Moving from GitHub to Codeberg, for lazy people

#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.

Re: Moving from GitHub to Codeberg, for lazy people

#56

Earlier quoted context omitted.

>On the other hand Codeberg doesn't let you create private repositories at all. are you sure about that? I'm fairly certain my repos on codeberg are all private but I could be mistaken.

It is kinda incorrect and kinda correct. Codeberg allows you to create private repositories. However, their rules are clear that the intent of private repositories must be in support of Free software projects: https://docs.codeberg.org/getting-started/faq/#how-about-pri... , which for many people is effectively not allowing private repositories.

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

Re: Moving from GitHub to Codeberg, for lazy people

#57
post #28

Earlier quoted context omitted.

For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…

If you can rsync from the other system, and likely have an SSH connection between them, why don't you just add it as an additional remote and git pull from it directly?

I probably could. How does that work with uncommitted changes on the host? Would that be a problem?

Re: Moving from GitHub to Codeberg, for lazy people

#58

I 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…

Working with all these modern layers, I don't see why people bother so much about it. This is all upper level decision to centralize so they feel they keep control. As a dev I'm 100% confident life would be as least as pleasant without all this abysmal layers of remote services that could all be replaced with distributed solutions that work 100% in local with thin sync step here and there.

Re: Moving from GitHub to Codeberg, for lazy people

#59

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…

> They also don't want to host your homepage, so if GitHub Pages is why you used GitHub, they are not a replacement. https://docs.codeberg.org/codeberg-pages/

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 seems more like it's meant for projects and organizations rather than individual people. The way it's described here indicates that using them to host your own blog/portfolio/what have you is considered to be abusing their services.

Post reply on HN