I have enjoyed using Forgejo over GitHub for local work. The features that GitHub has that plain Git does not includes a nice web renderer of markdown and code, issues and pull requests with comments, and project kanban boards. It's nice to have an alternative for local usage if GitHub ever goes down or just for private projects. Especially nice with agentic workflows, because agents can port issues, PRs, etc. back and forth between GitHub and Forgejo.
Moving from GitHub to Codeberg, for lazy people
131–140 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#132Earlier quoted context omitted.
I've had the same experience. Philosophically I think it's terrible that Cloudflare has become a middleman in a huge and important swath of the internet. As a user, it largely makes my life much worse. It limits my browser, my ability to protect myself via VPNs, etc, and I am just browsing normally, not attacking anything. Pragmatically though, as a webmaster/admin/whatever you want to call it nowadays, Cloudflare is…
> 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…
So, basically iocaine (https://iocaine.madhouse-project.org/). It has indeed been very useful to get the AI scraper load on a server I maintain down to a reasonable level, even with its not so strict default configuration.
Re: Moving from GitHub to Codeberg, for lazy people
#133I just migrated our entire company off of github to gitlab self-hosted. So far so good. It's entirely behind tailscale so we don't have any SSO tax from gitlab and all of our CI runners are on EKS + an on-prem cluster with GPUs. If anyone needs help or motivation accomplishing the same, just reach out!
Did you also try Forgejo? If so, what are the differences between the two? I didn't even know GitLab had a self-hosted option. I assume it's probably better for Enterprise-grade projects, and dealing with CI/CD, actions, etc. But for smaller projects that just have issues and PRs and minor test suites, I assume Forgejo is the better lightweight option.
Re: Moving from GitHub to Codeberg, for lazy people
#134Earlier quoted context omitted.
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?
Roughly:
`ssh remote "cd $src/repo ; git diff" | git apply`
(You'll need to season to taste: what to do with staged changes, how to make sure both trees are in the same HEAD, etc)
Re: Moving from GitHub to Codeberg, for lazy people
#135Earlier quoted context omitted.
> git's whole raison d'etre […] was that you do not need online access to the repo server most of the time Not really. The point of git was to make Linus' job of collating, reviewing, and merging, work from a disparate team of teams much less arduous. It just happens that many of the patterns needed for that also mean making remote temporarily disconnected remote repositories work well.
The whole point of git was tm be a replacement for BitKeeper after the Linux developers got banned from it for "hacking" after Andrew Tridgell connected to the server over telnet and typed "HELP"
That too, though the point of using a distributed code control system was the purpose I mentioned. But even before BitKeeper getting in a tizzy about Tridgell's¹ shenanigans there was talk of replacing it because some properties of it were not ideal for something as large as the kernel with as many active contributors, and there were concerns about using a proprietary product to manage the Linux codebase. Linus was already tinkering with what would become the git we know.
--------
[1] He did a lot more than type “help” - he was essentially trying to reverse engineer the product to produce a compatible but more open client that gave access to metadata BitKeeper wanted you to pay to be able to access² which was a problem for many contributors.
[2] you didn't get the fulllest version history on the free variants, this was one of the significant concerns making people discuss alternatives, and in some high profile cases just plain refuse to touch BitKeeper at all
Re: Moving from GitHub to Codeberg, for lazy people
#136I'm self-hosting Forgejo on my own home server. It's super easy to do via Docker or as a single binary executable. I even have CI/CD runners on it, which was also very easy to set up. Definitely recommend for those who might not want to rely on someone else, be it Codeberg or not, but still get the same quality as Codeberg (as they literally run Forgejo themselves).
Re: Moving from GitHub to Codeberg, for lazy people
#137I just migrated our entire company off of github to gitlab self-hosted. So far so good. It's entirely behind tailscale so we don't have any SSO tax from gitlab and all of our CI runners are on EKS + an on-prem cluster with GPUs. If anyone needs help or motivation accomplishing the same, just reach out!
Did you also try Forgejo? If so, what are the differences between the two? I didn't even know GitLab had a self-hosted option. I assume it's probably better for Enterprise-grade projects, and dealing with CI/CD, actions, etc. But for smaller projects that just have issues and PRs and minor test suites, I assume Forgejo is the better lightweight option.
Yeah I tried hosting forgejo and the first issue I found was that it was crashing some of the time with our large monorepo and getting actions/runners up and running was proving time consuming; I really did like how lightweight it was, monolith wise. gitlab has a lot more architecture behind it but the documentation is very good at describing how you should configure it for your needs.
I think Forgejo would work fine for smaller projects and teams. We really wanted to stop having to worry about GitHub going and not being able to do CD as well as get away from a lot of the action zero-days happening.
And yes, it's self-hosted and free! You can run a reference implementation pretty easily with non-production components (i.e. they won't backup or scale well).
Re: Moving from GitHub to Codeberg, for lazy people
#138Earlier quoted context omitted.
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 seem…
That FAQ snippet is insane to me. Maybe it's a cultural thing but I'd never do business with a company that has implicit threats in their ToS based on something so completely arbitrary.
The worst part is really the unclear procedure. If they set out terms that say they'll give me 4 weeks to migrate projects they don't like off the platform, with n email reminders in between, then that's not ideal but fine. As it is, I'd be worried I'll wake up to data loss if they get 'unhappy'. I have the same problem with sourcehut, actually, with their content policy.
Re: Moving from GitHub to Codeberg, for lazy people
#139I wish they had a paid plan for private repositories that aren't FOSS.
I recently ran across codefloe[1] recently in another thread[2], and have been considering it for private non-floss-related repos... haven't tried it out yet though, so mileage may vary. [1]: https://codefloe.com/ [2]: https://news.ycombinator.com/item?id=47487436
I've been using codefloe for everything personal, and I couldn't be happier. It's been stable, snappy, and offers me everything I need. I don't miss GitHub a single bit
Re: Moving from GitHub to Codeberg, for lazy people
#140Earlier quoted context omitted.
How do people even on hacker news of all places conflate git with a code hosting platform all the time? Codeberg, GitHub or whatever are for tracking issues, running CI, hosting builds, and much more. The idea that you shouldn't need a code hosting platform because git is decentralized is so out of place that it is genuinely puzzling how often it pops up.
OP didn't conflate them. They said they want to be able to rely on their git remote. The people responding are saying "nah, an unreliable remote is fine because you can use other remotes" which doesn't address their problem. If Codeberg is unreliable, then why use it at all? Especially for CI, issues, and collab?
The person you’re replying to is saying that you can do everything outside of tracking issues, running CI, ... without a remote. Like all Git operations that are not about collaboration. (but there is always email)
Maybe a hard blocker if you are pair programming or collaborating every minute. Not really if you just have one hour to program solo.