Set up source control on its own server

To make code repositories available for your site, install your source control application on a separate server and set up CollabNet TeamForge to use it.

  1. Set up your Subversion, CVS or Perforce server and make sure it is accessible on the network.
    Note: For installations on 64-bit Red Hat 5.4, communication between the source control integration server and the application server (where the main site runs) must be direct, and not through a proxy server.
  2. On the host that is to be your source control server, download the TeamForge installer package. See Get CollabNet TeamForge 5.4 for instructions.
  3. Unpack the main installation package.
    • rpm -ivh TeamForge-installer-5.4.0.0-308.noarch.rpm
    Tip: To specify the directory where you want the installation package deployed, add the --prefix flag to the rpm command.
    • rpm -ivh TeamForge-installer-5.4.0.0-308.noarch.rpm --prefix /some/other/path
  4. On the host where your main TeamForge application is running, open the teamforge-installer/<release-number>/conf/site-options.conf file.
  5. Under "Application settings" in the site-options.conf file, create (or reuse) a HOST_<hostname> token to specify the machine where the source code management service will run. For example:
    • HOST_codebox.supervillain.org=subversion
    Note: You can specify subversion, cvs, or perforce.
  6. Edit the existing HOST variable to reflect the fact that your source control service is no longer running on that machine. For example, suppose your organization, SuperVillain Inc., has a machine called appbox.supervillain.org available for its site to run on and a machine called codebox.supervillain.org for its Subversion integration. Your site-options.conf file will now look like this:
    • HOST_appbox.supervillain.org=app database
    • HOST_codebox.supervillain.org=subversion
  7. Copy the site-options.conf file to the teamforge-installer/5.4.0.0/conf directory on the source code machine.
    • scp conf/site-options.conf <subversion_server>://opt/collabnet/teamforge-installer/5.4.0.0/conf/
    • scp conf/site-options.conf <cvs_server>://opt/collabnet/teamforge-installer/5.4.0.0/conf/
  8. Install TeamForge on your source control server as instructed in Install the CollabNet TeamForge application (skipping the instructions for setting up a database).
Your users can now create and manage source code repositories from inside their TeamForge site.