Live data from Hacker News

Codeberg Is Down

social.anoxinon.de

31–40 of 53 posts

Re: Codeberg Is Down

#31

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.

Do you not spend much time writing and discussing issues or reviewing code?

Re: Codeberg Is Down

#33

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.

Re: Codeberg Is Down

#34

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.

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.

Re: Codeberg Is Down

#35

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. [1] https://forgejo.org/docs/v15.0/user/repo-mirror/

I am using it to backup my public and private repositories to Github and it's effortless, indeed. I am using ssh protocol and a read/write deployment key. Also, I anticipated `git push --force` could be an issue, it's not.

Re: Codeberg Is Down

#36

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.

Do you not spend much time writing and discussing issues or reviewing code?

You could use separate tools for those tasks. JIRA/Bugzilla/etc. for issue tracking, Sublime Merge or equivalent for comparing a dev branch to a main branch, and CI/CD with Azure Pipelines or whatever the “modern” equivalent of Jenkins is.

That isn’t as convenient as an all-in-one tool, and might not be what the user you’re responding to is doing. But it’s doable.

Re: Codeberg Is Down

#37
post #25

Earlier quoted context omitted.

Codeberg runs open source Forgejo, and you could on-prem that too (for no license cost), if it suits your needs. GitLab is more powerful in some ways, but early startups might want to look at Forgejo first.

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

Depends on the nature of your startup, and if you have significant infrastructure/architrcture for your workload or not. If you have significant scale you likely have a DevOps / SysAdmin type.

Re: Codeberg Is Down

#39

Earlier quoted context omitted.

Do you not spend much time writing and discussing issues or reviewing code?

You could use separate tools for those tasks. JIRA/Bugzilla/etc. for issue tracking, Sublime Merge or equivalent for comparing a dev branch to a main branch, and CI/CD with Azure Pipelines or whatever the “modern” equivalent of Jenkins is. That isn’t as convenient as an all-in-one tool, and might not be what the user you’re responding to is doing. But it’s doable.

Mailman provides decentralized issue tracking.
Post reply on HN