Oh FOSS projects I totally understand. It's where I go to too.
But closed source companies surly don't need to establish a community?
But closed source companies surly don't need to establish a community?
I've tried so many times in the past to argue for self-hosted setup that you fully control if you can afford it, things just get so much smoother and if you're a software development company, you probably want to own the software development workflow E2E so you can actually ship as fast as you want.
I know developers love to build, but do you think:
1) self-hosting git provides any competitive edge to the business over letting someone manage it?
2) it provides so much value that you’re willing to fund engineers to build, secure, support this on an ongoing basis?
I’ve found the answer to those is No in both cases.
The same reason you wouldn’t build your own internal chat tool, you’d use Slack. And you wouldn’t bother self-hosting your own Jira or documentation.
Code hosting is code hosting, there’s no difference where it's hosted. There’s no slowdown in delivery with using GitHub - their March uptime was 99.5% which annoys some commenters but it’s fine. That’s 45 minutes downtime per month which is tolerable.
You would spend way more effort and money building a jenky self-hosted solution to end up with a worse result.
Edit: to be clear for anyone reading, don’t do this, it’s a really bad idea. You need to patch your stuff, even behind a VPN. If you’re unsure, just google: “examples of security breaches of unpatched software behind VPNs”
If someone wants to pay me to do lead such an effort, I'd do it, and yes, it'll all be done and managed in code, and it will be done better than 90% of folks could do (I've seen the production build systems most environments have built, some big names too, and they're trash...in no small part because it's simply hard to do), but it'll take a while to smooth the experience out for all of your requirements. You're gonna be paying, and very well, for a while.