git - DVCS with a Windows central repository -
We are currently using VSS for the current version control. Many of our developers are interested in distributed models (and they want to get rid of VSS) Our network is full of Windows machines and our IT department has experience of maintaining a Linux machine, while they do not want to.
The DVCS system can host its central repository on Windows, while pushing access to the
- repository while providing.
- Basic authentication is mostly just one way that the permission to access or reject the entire repository.
- The server process does not require users to write for the repository reducing the risk of accidentally messing with it.
The customer will have at least one need for a GUI such as a GUI on the side (Sorry, the Windows Shell is useless.) The ease of installation will be very large because our IT department is already There is much less on resources. And the use of windows credentials for authentication will be a benefit, but unless the client is able to store the credentials, there will be no need.
I had a (really) quick look in the guit, mercurial and market. / P>
- For users requiring write permission for Git , SAP or Simple WebDAV wanted to use for repository access.
- Mercurial was built on an HTTPS server, but it seemed that for the purposes of the bridge, only update: Mercurial also supports push Does.
- Markets were seen to use sftp for repository access, then users need a written permission.
Is there any Windows Server procedures for DVC systems and is anyone able to set one in the Windows Land?
And if this is a duplicate question, I could not find any one.
Update
Mercurial work was found for push purposes! Detailed list what was needed, can be found in the form given below.
Mercurial is almost certainly your easiest choice on Windows.
If you do not care about authentication, then you can actually push hg service to push so that you can only push the following code The .hg / hgrc file must be added to the repository that you want to serve:
[web] allow_push = * push_ssl = false The first line says that anyone can push this repository. The second indicates that the SSC will run without the chair, because hg service currently does not support HTTPS natively. At this point, users can push anywhere in their repository without an account, if you are just a small shop, then this is probably okay - especially since you have a higher level of comparison than the basic basic than the basic mercurial You can use the ability to sign changes to ensure verification.
A big, shop, though, would be perfect for you to earn at least a simple barrier to earn. To do this, you have to make two changes. First of all, you must keep the mercurial behind a web server with reverse proxy support or CGI support. Thankfully, recent versions of IIS support both. You can consult Mercurial-specific steps, and support for the IIS side.
Next, you have to set up some basic authentication. IIS offers an HTTP Basic Out-The-Box, which can authenticate against your domain directly as a bonus, to keep the administrative overhead minimal.
Finally, you have to support only specific users by specifying a comma-delimited list of allow_push line usernames. For example:
allow_push = Benjamin, Ted, the_cow That's it. Seasonal will now allow users to authenticate via HTTP Basic authentication, and allow everyone to drag.
Comments
Post a Comment