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.
Moving from GitHub to Codeberg, for lazy people
51–60 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#52Codeberg vs selfhosted Gitlab. What do you think?
Re: Moving from GitHub to Codeberg, for lazy people
#53Earlier 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…
Re: Moving from GitHub to Codeberg, for lazy people
#54Lazy 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]
Re: Moving from GitHub to Codeberg, for lazy people
#55Re: Moving from GitHub to Codeberg, for lazy people
#56Earlier 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.
Re: Moving from GitHub to Codeberg, for lazy people
#57Earlier 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?
Re: Moving from GitHub to Codeberg, for lazy people
#58I 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…
Re: Moving from GitHub to Codeberg, for lazy people
#59I 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/
> 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.