Has anyone used the Repository Mirroring Feature [1] to mirror repos across self-hosted Forgejo/Codeberg/Github? How effortless is it? Ideally, I'd like to only ever push repos/branches to my self-hosted Forgejo, and have those changes automatically reflected on Codeberg/GH without thinking about it.
I suppose this is a good opportunity to ask, why do people get so affected by DVCS hosts going down? You can work locally with Git without uploading every change. Despite the constant reported GitHub downtime, I have not ever been adversely affected even once, since pushing and pulling are done every few days and I can freely branch/commit/merge locally.
Nowadays, these code forges have also become a centralized place for issue tracking, kanban boards, wiki editing and, specially, as CI/CD servers, in the case of GitHub Actions, which are, sometimes, the only for you to deploy software to package repositories. The same limitations apply to GitLab CI or Codeberg's Forgejo Runners/Woodpecker.
Whenever GitLab, Codeberg, BitBucket and, mostly, GitHub goes down, a lot of the software and websites you use can't be updated, including dependencies of your software that you're pulling from npm, for instance.
Finally, companies use code forges mostly for the ease of doing code reviews through Pull Requests/Merge Requests. Developers rarely, if ever, actually merge branches locally, before having it reviewed by peers in one of these code forges.
Git is a DVCS, but many companies have a build server/cluster that depends on Github or Codeberg being available.
Teams I've worked on for the last several decades aim to push 10-20 builds per day to external alpha testers, so any downtime in Github is going to be an impediment.
Since Sunday 00:18 CEST, Codeberg.org is offline. From our investigation, our primary location lost power in our racks, leaving the majority of our servers and some network switches offline. We're waiting for a fix from the datacenter operator.
" from that status page.
That, or the massive lightning that's going through the region, (due to the heatwave). Since it's quite late at night, heat wouldn't be my first guess.
I wonder what it's resonant frequency is.
[1] https://forgejo.org/docs/v15.0/user/repo-mirror/
Whenever GitLab, Codeberg, BitBucket and, mostly, GitHub goes down, a lot of the software and websites you use can't be updated, including dependencies of your software that you're pulling from npm, for instance.
Finally, companies use code forges mostly for the ease of doing code reviews through Pull Requests/Merge Requests. Developers rarely, if ever, actually merge branches locally, before having it reviewed by peers in one of these code forges.
Teams I've worked on for the last several decades aim to push 10-20 builds per day to external alpha testers, so any downtime in Github is going to be an impediment.
"Power Outage
Since Sunday 00:18 CEST, Codeberg.org is offline. From our investigation, our primary location lost power in our racks, leaving the majority of our servers and some network switches offline. We're waiting for a fix from the datacenter operator. " from that status page.
GitLab is more powerful in some ways, but early startups might want to look at Forgejo first.
Sorry, but there are a million things to do. Paying someone to self-host Forgejo isn't even on that list. We'll just pay someone at the moment.
This strikes me as odd, only three servers?
This is why it's getting traction.