I can be both bored and engaged, don't test me buddy /s
> equivalent of getting a surprise snow day
Not if you self-host Git
Re:GitHub Outage
by capableweb on Tuesday September 06, 2022 @08:24AM
(#32736160)
Self-hosting Git is easy, throw up a ssh server and point git to it.
Self-hosting everything else GitHub does is harder. Which is why they are building out all of those things, they don't want people to move to other places so easily.
Hopefully these constant outages makes more developers pissed off that issues are not stored in git as well, and start working on tooling to solve this shitty problem once and for all.
P2P/Local First software for everyone! \o/
Re:GitHub Outage
by chrisseaton on Tuesday September 06, 2022 @08:25AM
(#32736175)
> Self-hosting everything else GitHub does is harder.
You can self-host the whole of GitHub can’t you?
Re:GitHub Outage
by capableweb on Tuesday September 06, 2022 @08:41AM
(#32736316)
As far as I know, you can self-host an enterprise version of GitHub, but it'll still be available from one location (the server you deploy it on). I cannot run it locally and federate with my colleagues instances for example, just like I can with Git.
gitlab
Re:GitHub Outage
by capableweb on Tuesday September 06, 2022 @08:28AM
(#32736207)
GitLab is not P2P/Local First software like Git itself. It suffers from exactly the same problem as GitHub, reliance on a central server (which is run either by the company making the product, or by your own team).
What I'm talking about is being able to access everything like issues, wikis, PRs and whatever, even when you're 100% offline.
fair, i'd love that!
Not really. I'd rather be getting stuff done. ¯\_(ツ)_/¯
edit: oopsie I misread.
Would you characterise yourself as a bored engineer?
For engaged, happy engineers its the equivalent of getting a surprise snow day when you are grown up and have to go dig your car out of the snow and its a normal day just with extra steps.