4 ms·
I'm genuinely curious: what exactly is so hard about installing and system administering one's own servers inhouse that so many people would put up with these c
by Annatar 8y ago
I'm genuinely curious: what exactly is so hard about installing and system administering one's own servers inhouse that so many people would put up with these complications?
- sl1ck731 8y agoFor us its: availability outside of VPN and avoiding the run around of making a public site with security, integration with active directory, has repos + a wiki + boards all in one place. No configuring 3 different OSS products to integrate with AD. We use the other stuff more than the CI, but will probably begin using it for some more smaller projects soon. It'll be in the same place which is great and no need to tinker with servers which is awesome.
- chupasaurus 8y agoIf you have problem with configuring service users in AD, I guess you have problems with security or group policies on a regular basis.
- sl1ck731 8y agoOr AD isn't our responsibility and we can just use the tool (Azure devops) that is already done before we even launch it and provides all the features we need? I guess you don't have more important things to be doing than screwing with ancillary tools.
- patrickg_zill 8y agoThere isn't any true difficulty; people are running multiple sites that could all fit into 1 dedicated 64gb RAM server from Hetzner on a different infrastructure that allows them to develop their resume...
- Annatar 8y agoAre you saying that it's simply a case of resume inflation at employer's expense?
- patrickg_zill 8y agoSometimes yes. It's not just DevOps but CVops :-)
- Annatar 8y agoIf I catch anyone at my company doing CVops, there will be hell to pay. Not at the company's expense and certainly not on my watch!