6 ms·

Seriously considering moving our projects off of GitHub at this point. What other services are good? I loved using Phabricator at Facebook, but its cloud opti

Seriously considering moving our projects off of GitHub at this point. What other services are good? I loved using Phabricator at Facebook, but its cloud option is pricy.

boudin 7y ago
I'm considering self-hosting gitlab.
- reledi 7y ago
  Having been down that road, it's also a mess. Best I can imagine now is using GitHub as a primary and other hosted services as a mirror. Mirroring the git repos will only get you so far though, you won't have the services built around them (e.g. issues, merge requests, comments, actions) or you may not be mirroring all git repos that you need access to. But a reduced service may be sufficient for short periods during an outage.
  - leesalminen 7y ago
    How so? We've been self-hosting Gitlab for 2.5 years now (maybe more?). Besides a regular update (through apt) we haven't had any trouble. Team of 5 developers w/ a dozen or so repos and basic CI/CD builds. I highly recommend it.
    - reledi 7y ago
      We didn't have a better SLA than hosted GitHub when self-hosting GitLab, and then there's the extra cost of maintaining the instance, the CI runners, the DB, the networking, configuration and so on. Wasn't worth it for us after using self-hosted for 2+ years with a tech team ranging between 10-25. On top of that, most of the team thinks GitHub has a better UX and enjoy using it more.
  - boudin 7y ago
    Can you share your experience?
dubcanada 7y ago
Host it locally or on your own server?
djhaskin987 7y ago
There are tons of options. The most stable, well run, fully-featured of them is gitlab.com . GitHub recently changed its pricing model for teams private teams to try to compete with gitlab.com . Their feature set is absolutely fantastic and the site is one run by an independent and exemplary company. I've also been experimenting with sircmpwn's git.sr.ht, if you are a minimalist to me like that as well.
chatmasta 7y ago
In my experience, it's not really git itself that is the problem with downtime, but rather things like CI and recently, package registry. Last week I thought I was isolated from the GitHub downtime because I was working on a project on GitLab. But turns out a bunch of the npm dependencies are hosted on GitHub. Normally that wouldn't be a huge problem, except I'm specifically working on CI pipelines at the moment so it's quite frustrating.
- leesalminen 7y ago
  Came here because my Gitlab CI/CD was failing on `npm install` with a 500 from codeload.github.com.
  - chatmasta 7y ago
    And now they've bought npm as well! We're cornered.
ddevault 7y ago
Consider mine: https://sourcehut.org https://sourcehut.org It's a different workflow, but we've had zero unplanned outages in 2020 and are the highest performance software forge in general: https://forgeperf.org https://forgeperf.org
Seirdy 6y ago
If you have multiple remotes, then downtime quickly becomes a non-issue. As long as at least one remote is up, you can keep pushing and fetching. I wrote about mirroring in another comment [2]: > I put together a script [0] to automate the process to set the primary remote to Sourcehut (git.sr.ht) and mirror to GitLab and GitHub. And yes, that script is in a repo that's also mirrored to GitHub and GitLab (check the README). It combines well with my `git pushall` alias [1]. > [0]: https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/shell-scripts/bin/git-remote-setup https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/s... > [1]: https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/git/config#L41 https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/git/c... Bonus points for having one remote being a tiny self-hosted instance, like plain git+ssh. I don't think I've had any reliability issues with plain git+ssh on an rbpi. Furthermore, using mailing lists or something like git-bug instead of a vendor-locked-in issue-tracker keeps issues decentralized and eliminates downtime. [2]: https://news.ycombinator.com/item?id=22764055 https://news.ycombinator.com/item?id=22764055

Seriously considering moving our projects off of GitHub at this point. What other services are good? I loved using Phabricator at Facebook, but its cloud option is pricy.

boudin 7y ago

I'm considering self-hosting gitlab.

reledi 7y ago
Having been down that road, it's also a mess. Best I can imagine now is using GitHub as a primary and other hosted services as a mirror. Mirroring the git repos will only get you so far though, you won't have the services built around them (e.g. issues, merge requests, comments, actions) or you may not be mirroring all git repos that you need access to. But a reduced service may be sufficient for short periods during an outage.
- leesalminen 7y ago
  How so? We've been self-hosting Gitlab for 2.5 years now (maybe more?). Besides a regular update (through apt) we haven't had any trouble. Team of 5 developers w/ a dozen or so repos and basic CI/CD builds. I highly recommend it.
  - reledi 7y ago
    We didn't have a better SLA than hosted GitHub when self-hosting GitLab, and then there's the extra cost of maintaining the instance, the CI runners, the DB, the networking, configuration and so on. Wasn't worth it for us after using self-hosted for 2+ years with a tech team ranging between 10-25. On top of that, most of the team thinks GitHub has a better UX and enjoy using it more.
- boudin 7y ago
  Can you share your experience?

dubcanada 7y ago

Host it locally or on your own server?

djhaskin987 7y ago

There are tons of options. The most stable, well run, fully-featured of them is gitlab.com . GitHub recently changed its pricing model for teams private teams to try to compete with gitlab.com . Their feature set is absolutely fantastic and the site is one run by an independent and exemplary company. I've also been experimenting with sircmpwn's git.sr.ht, if you are a minimalist to me like that as well.

chatmasta 7y ago

In my experience, it's not really git itself that is the problem with downtime, but rather things like CI and recently, package registry. Last week I thought I was isolated from the GitHub downtime because I was working on a project on GitLab. But turns out a bunch of the npm dependencies are hosted on GitHub. Normally that wouldn't be a huge problem, except I'm specifically working on CI pipelines at the moment so it's quite frustrating.

leesalminen 7y ago
Came here because my Gitlab CI/CD was failing on `npm install` with a 500 from codeload.github.com.
- chatmasta 7y ago
  And now they've bought npm as well! We're cornered.

ddevault 7y ago

Consider mine: https://sourcehut.org https://sourcehut.org It's a different workflow, but we've had zero unplanned outages in 2020 and are the highest performance software forge in general: https://forgeperf.org https://forgeperf.org

Seirdy 6y ago

If you have multiple remotes, then downtime quickly becomes a non-issue. As long as at least one remote is up, you can keep pushing and fetching. I wrote about mirroring in another comment [2]: > I put together a script [0] to automate the process to set the primary remote to Sourcehut (git.sr.ht) and mirror to GitLab and GitHub. And yes, that script is in a repo that's also mirrored to GitHub and GitLab (check the README). It combines well with my `git pushall` alias [1]. > [0]: https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/shell-scripts/bin/git-remote-setup https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/s... > [1]: https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/git/config#L41 https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/git/c... Bonus points for having one remote being a tiny self-hosted instance, like plain git+ssh. I don't think I've had any reliability issues with plain git+ssh on an rbpi. Furthermore, using mailing lists or something like git-bug instead of a vendor-locked-in issue-tracker keeps issues decentralized and eliminates downtime. [2]: https://news.ycombinator.com/item?id=22764055 https://news.ycombinator.com/item?id=22764055