Earlier quoted context omitted.
"Just run gitea/gogs in a raspberry pi in the closet, works for me"
I hide mine in a Barnes & Noble
That should do it.
GitHub Outage Currently Ongoing – Issues, PRs, Notifications
81–90 of 106 posts
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#82Earlier quoted context omitted.
I tried gitlab but I hated the web interface. It was lacking in so many departments. Any other alternatives to github to try?
This. The UI is quite primitive compared to GitHub IMHO. That and Gitlab is littered with half-implemented or poorly implemented workflows. The MR workflow to support code reviews was never really thought through.
Hi, GitLab employee, is there anything else (besides the MR workflow) specifically that you think we should improve? UI-wise or whatever else you've noticed
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#83Earlier quoted context omitted.
> Git is distributed but all the things around it that we really need aren't Can anyone recommend an issue tracker that is distributed with the repo?
@TODO comments strewn around in your repo.
I was thinking of something that wouldn't be affected by the git history. There's no point in having branches for issue comments.
Something like:
$ git issue add "foo doesn't work"
Created issue ece5591: foo doesn't work
$ git issue comment ece5591 "the problem might be with bar"
Created comment 0191fa1 on issue #10.
$ git issue comment --reply 0191fa1 "or with baz"
Created comment f98e783 on issue #10.
$ git issue show ece5591
foo doesn't work -- ece5591 Your Name
the problem might be with bar -- 0191fa1 Your Name
or with baz -- f98e783 Your Name
$ git issue push
Pushed issues ece5591.
$ git issue pull
Pulled issues 3ebdc7e, 24cdb90.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#84I see posts like this make the front page of hacker news every so often, but I don't recall seeing posts about things like making list outages for something like the LKML (Linux Kernel Mailing List) or an IRC network like Freenode.
> IRC network like Freenode
When was the last time ALL freenode servers were offline? I know about occasional netsplits but those do not affect all of their servers and freenode itself is still operational.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#85Earlier quoted context omitted.
> When my whole country and some was suddenly denied all google services > didn't make any news here either Denied by government by any chance? Makes sense why it din't hit the news.
Denied by google engineers making a mess with router misconfiguration. The internet traffic at key points went down by ~30% just by google taking itself offline. Also what was fun was everyone being blocked from all services that use reCAPTCHA.
God... reCAPTCHA needs to die. I refuse to use any websites that use it!
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#86If you don't the the "community" features of GitHub, we have had very good results with Amazon Code Commit. I've never experienced an outage, it's easy to manage, and very inexpensive.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#87Earlier quoted context omitted.
The problem is bad design and/or integration of components. VMS clusters over leased lines went years without outages. Record was 17 years at a rail yard. They also did rolling upgrades across both different OS versions and CPU architectures . The methods are public if any competitors want to match or exceed them: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na... These modern cloud services using Linux…
Modern apps are designed to deal with part of them being down - it is the core upgrade strategy. VMS clusters were (and modern equivalents are) awesome, but they have a different speed of innovation / development. It is a trade off - perfect uptime, but that new feature could take a year, or 99.9% uptime, but it can be written and deployed tomorrow.
Our Erlang nodes are never down. We do live code updates and have gone several years now with no downtime.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#88Git is designed as distributed VCS, so an outage of a centralized server should not matter too much. So far, the theory. Using Github excessively is the way back to centralization, nowadays handing control over to Microsoft. Everybody who is concerned (probably not too much) should have a look into alternatives.
Yea because the alternative (hosting git yourself on your own servers) will have better availability and few issues (UX just came to mind!)
https://about.gitlab.com/install/
So the UX point is moot. From there, it is just a matter of how much do you want to pay for availability (multizone replication, etc)
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#89Earlier quoted context omitted.
I tried gitlab but I hated the web interface. It was lacking in so many departments. Any other alternatives to github to try?
This. The UI is quite primitive compared to GitHub IMHO. That and Gitlab is littered with half-implemented or poorly implemented workflows. The MR workflow to support code reviews was never really thought through.
> The MR workflow to support code reviews was never really thought through.
Uh, I've been using this for quite some time in GitLab and never found it lacking. Curious what do you find missing there?
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#90Alright, cue the usual: Monoculture bad Microsoft bad Git is distributed but all the things around it that we really need aren't You can set up git to push to multiple remotes automatically Nobody is actually using git in distributed mode Did I forget anything?
The knowing meta-post.
And the meta-meta follow on.