Configure your CollabNet SourceForge Enterprise 5.1 site

To control the basic behavior of your CollabNet SourceForge Enterprise 5.1 installation, edit the values in the master site configuration file.

Everything about how CollabNet SourceForge Enterprise 5.1 works is controlled by settings in the master configuration file, site-options.conf. A number of other configuration files are installed, but they are not to be edited. CollabNet SourceForge Enterprise 5.1 generates the values in these files according to the values that you set in the master configuration file.

Note: This page describes the minimal steps you must take for your site to work. You can set other options if you know what you are doing.

Copy the master configuration file from the sample configuration file.
- cd <installation_source>/conf
- cp sample-site-options.conf site-options.conf
In the site-options.conf file, uncomment and rename the HOST_localhost token, replacing localhost with the name of the machine on which you are running SourceForge. For example, suppose your organization, Supervillain.org, wants the domain name worlddomination.supervillain.org for its development site, and a machine called bigbox.supervillain.org is available for the site to run on.
- HOST_bigbox.supervillain.org=app database subversion
Important: The host name is case-sensitive, and must exactly match the hostname as listed in the /etc/hosts file.
If the site is running on multiple hosts, specify where each component will run.
1. Create a new HOST_<hostname> token for each machine in your group. For each HOST_<hostname> token, specify the services that will run on that host. For example:
  - HOST_bigbox.supervillain.org=app database
  - HOST_svn.supervillain.org=subversion
  - HOST_perforce.supervillain.org=perforce
2. Specify the DOMAIN variable to point the site's domain name to the machine where the application is running. Use this format:
  - DOMAIN_<host_name>=<domain_name>
  For example:
  - DOMAIN_bigbox.supervillain.org=worlddomination.supervillain.org
Tip: This can also be useful if you are staging a site. In this case, provide a domain name like stage.worlddomination.supervillain.org.
Select and configure your database application.
1. Set the value of the DATABASE_TYPE variable to postgresql or oracle.
2. Set values for the other key database variables:
  - DATABASE_USERNAME
  - DATABASE_PASSWORD
  - DATABASE_NAME
Specify how you want site-related emails handled by giving values for these variables:
- SYSTEM_EMAIL: A valid email address for the system administrator responsible for this site.
- ADMIN_EMAIL: A valid email address for the site administrator.
- JAMES_POSTMASTER_EMAIL: A valid email address for the person or machine that handles email for the domain, such as postmaster@<supervillain.org>.
  Tip: The email accounts specified in the SYSTEM_EMAIL, ADMIN_EMAIL, and JAMES_POSTMASTER_EMAIL variables do not necessarily have to be different from each other.
- JAMES_GATEWAY_HOST: A mail server with Internet access. This assures delivery of site email to users if your SourceForge server cannot connect to a DNS server or cannot get outside connections over port 25.
Note: Any email account you specify for the site must be hosted on a separate server from the SourceForge site server.
Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation.
If your source control service is running on its own machine, copy the site-options.conf file to the <installation_source>/conf directory on that machine.
- scp conf/site-options.conf <subversion_server>:/<installation_source>/conf/
- scp conf/site-options.conf <cvs_server>:/<installation_source>/conf/