Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was down

githubstatus.com

Post reply on HN
Print view View original

51–60 of 133 posts

Re: GitHub was down

#51

Post by Evidlo »

sparkling wrote: post #36
rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

How about a more low-tech solution? I don't want/need a full-blown web application like Gitlab, just need somethings than auto-syncs my public and private repos so that i can still access everything when Github is down. Any ideas?

Just add another git remote push URL so that your commits are automatically mirrored when you push:

    git remote add origin https://user@gitlab.com/myrepo
    git remote set-url --push --add origin https://user@github.com/myrepo
    git remote set-url --push --add origin https://user@gitlab.com/myrepo

Re: GitHub was down

#52

Post by EGreg »

Evidlo wrote: post #37
rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

The downside is that a lot of these self hosted archives will have disappeared 10 years from now. Meanwhile, I expect many forgotten repos to remain online with Github one way or another for a very long time. If you do go the self-hosting route, add a mainstream host as an additional remote and push your commits to both.

This is a huge reason why they are making MaidSAFE. Anyone remember Freenet?

Re: GitHub was down

#53

Post by mukgupta »

kenhwang wrote: post #12
lprd wrote: post #8

This is slowly becoming a weekly occurrence ever since Microsoft entered the picture... https://www.githubstatus.com/

I remember it being a weekly occurrence before Microsoft as well. edit: though their historical data doesn't back it up. It's just a 2020 thing it seems; coincidentally picked up right near the middle of February which correlates way too closely with the beginning of COVID.

Might be a side-effect of working remotely because of covid

Re: GitHub was down

#54

Post by jopsen »

hamandcheese wrote: post #46
sparkling wrote: post #36

Earlier quoted context omitted.

How about a more low-tech solution? I don't want/need a full-blown web application like Gitlab, just need somethings than auto-syncs my public and private repos so that i can still access everything when Github is down. Any ideas?

The lowest tech solution is to just wait until the outage is over. It’s 100% free! Seriously, though, any repo that I work on regularly will be cloned to my local dev environment, so it’s not a hard blocker. That said, a cron job on a cheap VPS would probably do the trick.

Moreover, GitHub will eventually get these outages under control. Or we'll all be driven to gitlab :)

Re: GitHub was down

#55

Post by regecks »

Evidlo wrote: post #37
rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

The downside is that a lot of these self hosted archives will have disappeared 10 years from now. Meanwhile, I expect many forgotten repos to remain online with Github one way or another for a very long time. If you do go the self-hosting route, add a mainstream host as an additional remote and push your commits to both.

No guarantees either way - Google Code was alive and kicking, until it suddenly wasn't.

I do appreciate how easy git and other dvcs make it to mirror repositories, though. I find myself using Github mirrors of projects that are otherwise self-hosted, just because the code search works on Github works pretty well.

Re: GitHub was down

#56

Post by stabbles »

gitgud wrote: post #47
rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

True, but the burden of maintenance and up-time is on yourself then... Might be good to have a self hosted backup that's automatically synced with Github

You can easily do the latter with Gitlab, free for open source projects.

Re: GitHub was down

#57

Post by stunt »

lprd wrote: post #8

This is slowly becoming a weekly occurrence ever since Microsoft entered the picture... https://www.githubstatus.com/

I don't think it has anything to do with Microsoft acquisition. Perhaps they even have more compute power available since then.

But, they are moving much faster in recent years. They've added a lot of new features.

Re: GitHub was down

#58

Post by jopsen »

kenhwang wrote: post #12
lprd wrote: post #8

This is slowly becoming a weekly occurrence ever since Microsoft entered the picture... https://www.githubstatus.com/

I remember it being a weekly occurrence before Microsoft as well. edit: though their historical data doesn't back it up. It's just a 2020 thing it seems; coincidentally picked up right near the middle of February which correlates way too closely with the beginning of COVID.

I recall it happening many years ago too.. but GitHub seemed to eventually sort it out, I suspect they will this time too.

Re: GitHub was down

#60

Post by Evidlo »

regecks wrote: post #55
Evidlo wrote: post #37

Earlier quoted context omitted.

The downside is that a lot of these self hosted archives will have disappeared 10 years from now. Meanwhile, I expect many forgotten repos to remain online with Github one way or another for a very long time. If you do go the self-hosting route, add a mainstream host as an additional remote and push your commits to both.

No guarantees either way - Google Code was alive and kicking, until it suddenly wasn't. I do appreciate how easy git and other dvcs make it to mirror repositories, though. I find myself using Github mirrors of projects that are otherwise self-hosted, just because the code search works on Github works pretty well.

But the content is still available isn't it: https://code.google.com/archive/

When people try to self-host and get lazy or hit by a bus, the content just disappears unless it was lucky enough to get archived.

Post reply on HN