51–60 of 97 posts
Earlier quoted context omitted.
Github enterprise cloud is on github.com and with more features: http://github.com/account/enterprises/new They don't host github enterprise server for you (though gitlab has something called gitlab dedicated which they host gitlab ee for you).
Why is there an eu github status then ? https://eu.githubstatus.com/uptime
Earlier quoted context omitted.
A "reasonable" answer is probably a primary self-hosted Forgejo instance as the canonical forge, while using GitHub as a mirror solely to take advantage of its free CI, while that lasts, while hosting secrets with a dedicated secret-hosting provider (I don't know what the provider du jour for this is these days).
Replace a whole 24/7 team of devops people with myself? As much as I'd like to believe that I'm worthy, I'm not.
I was impressed enough by AI finding vulnerabilities in source code, but doing it in binary executables is just amazing. This has so much potential, good and bad. And yet another lesson to not treat data as instructions. Sanitize all user input!
As we have known for a while, they ended up being really good at translating source to source or text to source. It shouldn't be too surprising they are also really good at understanding the asm version too.
Doesn't make it any less impressive, but maybe less surprising.
Another tour de force from Wiz, and a watershed moment in AI tooling enabling RE and compromise discovery.
Another data point against doing security through obscurity.
Earlier quoted context omitted.
GitLab ?
The people who suggest gitlab, haven't used it. But I guess I could be tempted to try again... https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
Earlier quoted context omitted.
The people who suggest gitlab, haven't used it. But I guess I could be tempted to try again... https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
Ah, you assumed I meant SaaS GitLab. I meant the self-hosted version. I would never host our source code on a remote service.
Earlier quoted context omitted.
It's incredibly fragile. It breaks a vast majority of the time and takes multiple rounds of support on-call to upgrade typically.
Unsurprising for a fourth tier on-prem created by cutting a continuously deployed application into releases.