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…
Moving from GitHub to Codeberg, for lazy people
291–300 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#292Earlier quoted context omitted.
Actions are bad, but they're free (to start) and just good enough that they're useful to set up something quick and dirty, and tempt you to try and scale it for a little while.
Exactly. Any github alternative needs to consume same GithubActions syntax OOTB I'm afraid.
Re: Moving from GitHub to Codeberg, for lazy people
#293The 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.
GitHub also generously gives me a bunch of free CI, in exchange for whatever they benefit from me being there. It's worth $50 just this month, according to them, but I don't see anyone else offering the mac runners that account for most of it. For all the complaints, I test my packages that actually need it across dozens of architecture and OS combinations with a mix of runners, nested virtualization and qemu binfmt,…
Re: Moving from GitHub to Codeberg, for lazy people
#294Earlier quoted context omitted.
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.
> Finding an HTTP+FTP server was easier than finding github. No it wasn't. Seriously, where?
Re: Moving from GitHub to Codeberg, for lazy people
#295GitHub gives you a lot for "free". In exchange they'll have no problem harvesting your data, and it would really surprise me if they aren't training on private repos too. I guess you can opt out and if they're opt out doesn't work oh well. On the other hand Codeberg doesn't let you create private repositories at all. So Copilot could still legally scrape your open source Codeberg repos. I don't see much of a point fo…
Re: Moving from GitHub to Codeberg, for lazy people
#296Earlier quoted context omitted.
> Finding an HTTP+FTP server was easier than finding github. No it wasn't. Seriously, where?
There was a lot of sites that provided some cpanel-like option as long as you're ok with yourcoolname.weirdhostingname.com. I believe they all came with a filebrowser and the always present public_html folder.
Re: Moving from GitHub to Codeberg, for lazy people
#297Earlier 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.
I didn't misunderstand. Sshd is a web service. Most folks don't already know how and don't want to set up a machine that is always on, that will restart on power loss, that will have a static IP or dynDNS, with a domain name and proper routing and open ports and certs and enough bandwidth and that's before you even worry about actual security and not just what is needed to work.... It's actually a big annoyance if yo…
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 taken.Re: Moving from GitHub to Codeberg, for lazy people
#298Earlier quoted context omitted.
If it's your ssh server and it's single user you don't need to use the "git@" part at all. Just store the repo and access it with your account. The whole git@ thing is because most "forge" software is built around a single dedicated user doing everything, rather than taking advantage of the OS users, permissions and acl system. For a single user it's pointless. For anyone who knows how to setup filesystem permissions…
There isn't much advantage that can be taken from O/S users and perms anyway, at least as far as git is concerned. When using a shared-filesystem repository over SSH (or NFS etc.), the actually usable access levels are: full, including the abilities to rewrite history, forge commits from other users, and corrupt/erase the repo; read-only; and none.
Re: Moving from GitHub to Codeberg, for lazy people
#299Earlier 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…
Re: Moving from GitHub to Codeberg, for lazy people
#300Earlier 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…
Why not use VMs? Libvirt is scriptable enough for that. And LXC/Incus can be used if you want the shorter starting time.