Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
3 Corrected spelling
source | link

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project so you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuffstaff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuffstaff has access to data, which is much more critical and sensitive, that than source code. How do you plan to address this?

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project so you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuff has access to data, which is much more critical and sensitive, that source code. How do you plan to address this?

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project so you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your staff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your staff has access to data, which is much more critical and sensitive than source code. How do you plan to address this?

2 Corrected spelling
source | link

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project andso you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuff has access to data, which is much more critical and sensitive, that source code. How do you plan to address this?

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project and you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuff has access to data, which is much more critical and sensitive, that source code. How do you plan to address this?

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project so you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuff has access to data, which is much more critical and sensitive, that source code. How do you plan to address this?

1
source | link

There are multiple options except for Gitlab (including pure Git). But as Gitlab is open source/open code project and you can just install it on your private server, so nobody except your team will have access.

Which, raises, I believe, more prominent issue - your stuff know security holes or some sensitive configuration and could sell the source code to some third party or to the government. Even more - your stuff has access to data, which is much more critical and sensitive, that source code. How do you plan to address this?