4 ms·
The problem with self-hosting is one of managing the servers. When you are a small team the effort is just not worth it. Yes, there are risks when you give your
by vineet 14y ago
The problem with self-hosting is one of managing the servers. When you are a small team the effort is just not worth it. Yes, there are risks when you give your code to someone else, but hopefully a company whose job is to host source repositories will take enough precautions.
Note, you can host GitHub within your company, but again - it is usually not worth it unless you are a larger company.
- cpher 14y agoI've deployed Git on a server in our DMZ for testing. So, it's possibly accessible from external IPs, but in reality we're using it via a VPN connection, so it's mostly internal. I haven't locked down the security yet. My idea is to create an internal git server that is freely accessible when connected via VPN or secure HTTPS (when not on VPN). From what I've read, the self-hosted GitHub is far beyond our budget. We already have VM servers available. It's just a matter of choosing an appropriate self-hosted solution (e.g. WebGitNet, etc) vs. a more established and polished GitHub solution.