Configuring Apache for Subversion
Accessing Subversion Repositories via Apache has several advantages: neither extra port for external access nor SSH key setup is required.
This page describes how to setup Apache to Serve Subversion Repositories.
codeBeamer must be installed and started before this description can be used.
mod_evasive apache module must be disabled (if enabled) to ensure that remote-api and webdav work properly.
Windows
Please choose the 32 bits version of all software mentioned below even when running 64 bits Windows
This description assumes that codeBeamer has been installed into
C:\CB-5.5
.
- Edit the Apache configuration:
Click on
Start->All Programs->Apache HTTP Server 2.2->Configure Apache Server->Edit the Apache
httpd.conf
Configuration File!
Click on
Start->All Progeams->Apache HTTP Server 2.2->Configure Apache Server->Test Configuration
- If everything's fine restart Apache:
Click on
Start->All Programs->Apache HTTP Server 2.2->Configure Apache Server->Control Apache Server->Restart
Linux/Unix
It is important that codeBeamer operating system user and apache belong to the same GID!
Ubuntu
This description assumes that codeBeamer has been installed into
/home/codebeamer/CB
.
This will install and enable the modules required in order to user Subversion with Apache.
If everything's fine you can restart Apache:
sudo /etc/init.d/apache2 restart
RedHat
- Finally test the apache configuration:
apachectl configtest
If everything's fine you can restart Apache:
sudo /etc/init.d/httpd restart
How to checkout from a codeBeame repository and commit to it
- Create a new codeBeamer project with a Managed Mercurial Repository and the name of the repository should be svntest. Follow the steps described in
Creating Managed Repositories.
- Create a new issue in the Bugs tracker of the new project. This example assumes that the new issue gets the ID 1000 and the project was created by the account bond that has the password 007.
It is strongly NOT recommended using user/password in URL!
- Now after refreshing the browser window with issue details and the change set should appear under SCM Commits tab.