3 ms·
There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. An extreme case of that would be an a
by Xylakant 8y ago
There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. An extreme case of that would be an airgapped network. Company policy might require that code does not leave the company network. You might legal be compelled to have full control over your code and where it goes (think: code under export restrictions).
All of these people self-host and it solves a problem for them.
- geezerjay 8y ago> There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. It's also hard to justify routing traffic through different continents if all you want to do is share a repository with someone sitting at a desk right next to you.
- dijit 8y agoI think it also comes down to the availability of service or even not agreeing about the future of your hosting provider. Prime example is obviously github, why would my company host on github if they never made profit? that service could go away any time or the service could change in a way that is a pain for my company to migrate. It swings for other things you'd host, if I use services on Azure (such as Thunderhead) and I'm developing games, well Microsoft also develops games. I put my IP at risk.