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

GitHub is down

github.com

Post reply on HN
Print view View original

41–50 of 53 posts

Re: GitHub is down

#41

Post by pmlnr »

moron4hire wrote: post #37
kbutler wrote: post #21

Too bad git is a distributed version control system, so you have your repositories locally and can continue work without remote access.

The specific problem today is that I have changes on my home PC that I finished and pushed up to Github last night, but now I can't get them at work this morning, because my home PC is behind a firewall. Also, my IP address is not static, so there's no guarantee I'll even be able to find it to make it a remote.

All you need is to change a DNS entry once your ip changes. Or a remote port via ssh tunnel. (see -R option ).

Re: GitHub is down

#42

Post by weaksauce »

moron4hire wrote: post #37
kbutler wrote: post #21

Too bad git is a distributed version control system, so you have your repositories locally and can continue work without remote access.

The specific problem today is that I have changes on my home PC that I finished and pushed up to Github last night, but now I can't get them at work this morning, because my home PC is behind a firewall. Also, my IP address is not static, so there's no guarantee I'll even be able to find it to make it a remote.

Fwiw you can use a dynamic dns to connect to your computer if you poke holes in the firewall and feel like running ssh or something similar.

Re: GitHub is down

#43

Post by sairamkunala »

abhixec wrote: post #40
mbertschler wrote: post #30

Earlier quoted context omitted.

Instead of Gogs it is now recommended to use Gitea, since it has more activity (~400 more commits last time I checked) and is community driven: https://gitea.io/ According to their Blog: Gitea is a community fork of the popular self-hosted Git service Gogs. We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effor…

Is there any particular reason why this is recommended over Gogs?

Gitea is a community fork of the popular self-hosted Git service Gogs. We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model.

This happened not before trying to convince @Unknwon about giving write permissions to more people, among the community. He rightly considered Gogs his own creature and didn’t want to let it grow outside of him, thus a fork was necessary in order to set that code effectively free.

source: https://blog.gitea.io/2016/12/welcome-to-gitea/

Re: GitHub is down

#44

Post by koolba »

ComputerGuru wrote: post #16

Obligatory Gogs plug: https://gogs.io It also has an awesome automatic mirror mode that can remain sync'd to a remkte repository. I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

> I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

For your own code sure that works and you can keep working locally.

The problem is that a lot of build systems rely on downloading releases from GitHub. If your build process is borked it's damn near impossible to push a code change to production.

Re: GitHub is down

#45

Post by gravypod »

ComputerGuru wrote: post #16

Obligatory Gogs plug: https://gogs.io It also has an awesome automatic mirror mode that can remain sync'd to a remkte repository. I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

If you want something similar and easier to set up check out https://github.com/gitbucket/gitbucket

Re: GitHub is down

#46

Post by davedx »

ComputerGuru wrote: post #16

Obligatory Gogs plug: https://gogs.io It also has an awesome automatic mirror mode that can remain sync'd to a remkte repository. I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

But git is decentralized. Github is just a UI.

Re: GitHub is down

#47

Post by makmanalp »

davedx wrote: post #46
ComputerGuru wrote: post #16

Obligatory Gogs plug: https://gogs.io It also has an awesome automatic mirror mode that can remain sync'd to a remkte repository. I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

But git is decentralized. Github is just a UI.

Not when a lot of code / packages by default rely on github servers for hosting and delivery.

Re: GitHub is down

#48

Post by kamjam »

koolba wrote: post #44
ComputerGuru wrote: post #16

Obligatory Gogs plug: https://gogs.io It also has an awesome automatic mirror mode that can remain sync'd to a remkte repository. I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization.

> I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization. For your own code sure that works and you can keep working locally. The problem is that a lot of build systems rely on downloading releases from GitHub. If your build process is borked it's damn near impossible to push a code…

What happens when something like nuget.org/npm/other equivalents that you have a dependency on from your code/build system go down?

Unless you are self-hosting everything then there is a reliance on 3rd parties. Even when you self-host, you have a dependency on your IT team for maintenance - 100% uptime is impossible for anyone, servers sometimes need to undergo routine maintenance or an upgrade. Yes, I understand the difference being it's on your own timeframe, but often it's just been one of those things.

Even with these small outages, would be interested if anyone is able to keep higher uptime themselves.

Re: GitHub is down

#49

Post by abhixec »

sairamkunala wrote: post #43
abhixec wrote: post #40

Earlier quoted context omitted.

Is there any particular reason why this is recommended over Gogs?

Gitea is a community fork of the popular self-hosted Git service Gogs. We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model. This happened not before trying to convince @Unknwon about giving write permissions to more people, among the community. He rightly co…

ah my bad. I didn't realize that gogs was a single maintainer management model.

Re: GitHub is down

#50

Post by koolba »

kamjam wrote: post #48
koolba wrote: post #44

Earlier quoted context omitted.

> I don't care what your company does or how you run it, but please don't just rely on Github to host your code without a mirror somewhere. There are drawbacks to this incessant centralization. For your own code sure that works and you can keep working locally. The problem is that a lot of build systems rely on downloading releases from GitHub. If your build process is borked it's damn near impossible to push a code…

What happens when something like nuget.org/npm/other equivalents that you have a dependency on from your code/build system go down? Unless you are self-hosting everything then there is a reliance on 3rd parties. Even when you self-host, you have a dependency on your IT team for maintenance - 100% uptime is impossible for anyone, servers sometimes need to undergo routine maintenance or an upgrade. Yes, I understand th…

Exactly. For some build systems (ex: Maven or NPM) you can have a local proxy the mitigate a lot of this. It also has the advantage of having a fixed (hopefully validated!) set of dependencies instead of pulling it whatever wild-wild-west change there is in the latest version of something. It also insulates you from the historical changes.
Post reply on HN