Configure the site

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

Note: These are the minimal options that you must set. You can set other options if you know what you are doing.
  1. Create the working configuration file from the sample configuration file.
    Important: If you have already copied the configuration settings from an old site, skip this step.
    • cd <installation_source_directory>
    • cp conf/sample-site-options.conf conf/site-options.conf
  2. Open conf/site-options.conf with a text editor.
  3. Use the HOST variables to identify the machines where CollabNet SourceForge Enterprise 5.0 will run.
    1. Rename the HOST_localhost token, replacing localhost with the name of the machine on which you are running SourceForge. Create a new HOST_<hostname> token for each machine in your group.
    2. For each HOST_<hostname> token, specify the services that will run on that host. For example:
      • HOST_main.example.com=app database
      • HOST_svn.example.com=subversion
      • HOST_perforce.example.com=perforce
      Important: Make sure only one source control service is specified for any host.
  4. If users will access this site by a domain name, create a DOMAIN variable to specify the domain name. Use this format: DOMAIN_<host_name>=<domain_name>
    Important: If the site is running on multiple hosts, point the DOMAIN variable to the host where the SourceForge application is running.
    Tip: This can also be useful if you are staging a site. In this case, provide a domain name like stage.mysite.com.
    For example:
    • HOST_main.example.com=app database
    • ...
    • DOMAIN_main.example.com=catandmouse.org
  5. Choose string values for the database variables.
    Note: If you are upgrading from a SourceForge 4.4 site, you will probably want to keep the existing values.
    1. Set the value of the DATABASE_TYPE variable to oracle or postgresql.
    2. Set a value for DATABASE_USERNAME.
    3. Set a value for DATABASE_PASSWORD.
    4. Set a value for DATABASE_NAME.
  6. Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation.
    Tip: Pay special attention to these variables:
    • FILESTORAGE_LOCATION
    • SCM_REPOSITORY_ARCHIVE
    • DATA_DIR
  7. If your installation is to run on multiple machines, copy the configuration file to all the machines in the group.
    • scp conf/site-options.conf <second node>:/<install-directory>/conf/
    • scp conf/site-options.conf <third node>:/<install-directory>/conf/
    Note: If you are upgrading from a SourceForge 4.4 site that runs on multiple hosts, and you intend to replicate that setup on the new site, then repeat the process for each host.

    For example, if the old site has the application server and database on host1_44 and the Subversion integration on host2_44, run the generate-site-options.sh script two times

    1. Run the script on host1_44 and copy the resulting site-options.conf file to host1_50.
    2. Run the script on host2_44 and copy the resulting file to host2_50.
Related concepts
Which application runs on which server?
How many servers do I need to run a SourceForge site?
Related reference
site-options.conf