51–60 of 99 posts
Fixed in about 30m to an hour. Definitely annoying, but I'll try the hot take that, contrary to popular belief, GH is not critical infrastructure - or so I hope. Please tell me no part of the Ukrainian air defense system depends on a gh action hook.
Earlier quoted context omitted.
Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.
^ this. the last thing i want is to add to my workload. take my money and make my life easier, even if it means that for one hour every couple months i can't do anything
Earlier quoted context omitted.
Unless some major customers are moving away, I don't think they are going to seriously care about it.
I suspect some companies may already be considering it. Especially with the wealth of alternatives today.
helm repo add gitlab https://charts.gitlab.io/ && helm upgrade --install gitlab gitlab/gitlab I did this in 2019, it avoided so many headaches. CI is better too since there's a nice clean mapping of build -> pod for everything and I can just exec in if something's borked.
Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.
Earlier quoted context omitted.
What kind of alternatives do you see as viable for large(ish) commercial users?
GitHub on-prem. Officially called GitHub Enterprise Server. You can have GitHub, but hosted on your own servers.
Earlier quoted context omitted.
having no issues on azure here, seeing no azure incidents on the status page or any of my admin panels
> seeing no azure incidents on the status page … in all seriousness, that is hardly proof that Azure isn't having an outage.
its one signal, among others. and in any case, i wasn't trying to prove the parent commenter wrong. i was offering my own signal to the crowd.
Earlier quoted context omitted.
Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.
It depends how high you value your headaches, and how high, your org's downtime. Github not working accrues over the hourly rate of every developer affected, which is likely $70-$100 a hour. 10 hours of outage in a year affecting a team of 10 would cost north of $70k, enough to hire a part-time SRE dedicated just to tend to your Gitlab installation.
Earlier quoted context omitted.
Having just had to buy 4TB of RAM, I appreciate this.
That's like 100,000 USD. I keep thinking about making a rap video wearing a 10 TB gold chain surrounded by big booty girls with their naughty bits covered in m.2 SSD's while dissing the AI industry. Though I cant afford the RAM :-/
I was pissed that there weren't any sticks heading to the recycling out of the nodes otherwise I would make myself that chain :)
Earlier quoted context omitted.
Virtually no one knows how to do anything with it outside of github.
Your favorite search engine or LLM will show you in a second, it's really easy. The problem is that it's not enough. The fact that Github uses Git specifically is a technical detail; it could use mercurial equally easily, as Bitbucket used to. Github Actions, OWNERS files, PRs and review tools, issue tracker, wiki are all not Git features.
(I use Fossil 100% offline for personal projects for ref)