3 Configuration Guides for Setting Up Secure Git, Mercurial and Subversion Environments with Apache

While most VCS systems support the plain vanilla HTTP protocol with username and password authentication, this is a better idea to use a secure connection over SSH or HTTPS. Without that, your work, communication and intellectual property is vulnerable to various sniffing techniques. The problem is that setting up that environment on the server can be quite painful, unless you are sysadmin kind of guy.

To less the pain, we have written up step-by-step guides for the most popular version control system. These explain how to get them up and running with Apache HTTPD, leveraging its user management capabilities and the secure HTTPS protocol. Just follow the steps, and you will have a working secure DVCS environment in minutes!

Note: you must be logged in to JavaForge to access these pages. Sign up for JavaForge if you are not a community member yet.

• You must login to see this link. Register now, if you have no user account yet.
• You must login to see this link. Register now, if you have no user account yet.
• You must login to see this link. Register now, if you have no user account yet.

Why should I read these?

These configuration guides were originally written as part of the codeBeamer Administrator's Manual. They can be, however, applied to any other environment without changes, so we decided to move them to this new project here at JavaForge.

We are encouraging you to contribute to the guides, by testing the procedure on other operating systems, adding hints and shortcuts, and just telling us how to improve them.

Important note: if you want to make your life easier, you should try our software, codeBeamer. It automates parts of the process and offers fully web based user management, access control and repository management for Git, Mercurial and Subversion. Please see the codeBeamer downloads in the right.