Install TeamForge 6.1.1 the easy way

The easiest way to install TeamForge is to install on a single box, dedicated to TeamForge only, taking the default configuration settings. We call this a "dedicated" install.

1. Install CentOS 5.6 and log in as root.
   • See Platform specification for TeamForge 6.1.1 for the full platform requirements.
   • See the Red Hat installation guide for help.
   Important: Don't customize your installation. Select only the default packages list.
2. Uninstall the PostgreSQL support package and the Dovecot mail server to clear the way for TeamForge to install PostgreSQL 9.0.4. These packages are installed as part of the default CentOS install.
   • yum erase postgresql-libs dovecot
3. Check your basic networking setup. See Set up networking for your TeamForge box for details.
4. Download the TeamForge 6.1.1 installation repository from open.collab.net. Copy it to /etc/yum.repos.d/.
5. Install the TeamForge application.
   • yum install teamforge
   Tip: If the yum installer balks, you may have duplicate rpm packages.

   1. Get the yum-utils package, if it isn't already installed.
      • yum install yum-utils
   2. Check for duplicate packages.
      • package-cleanup --dupes
   3. Clean up the older packages, if any.
      • package-cleanup --cleandupes
   4. Rerun the yum installer.
      • yum install teamforge [options]
6. Set up your site's master configuration file.
   • vi /opt/collabnet/teamforge-installer/6.1.1.0/conf/site-options.conf
   Note: vi is given as an example. Emacs, gedit, or any other *nix text editor will also work.

   At this stage, we'll make the minimal modifications required to set up a usable TeamForge 6.1.1 site.

   1. Edit the DOMAIN_localhost variable to point the site's URL to the server where the site is running. Use this format:
      • DOMAIN_localhost=<domain_name>
      For example, suppose SuperVillain Inc. wants its development site to have the URL https://worlddomination.supervillain.org. The DOMAIN_localhost variable will look like this:
      • DOMAIN_localhost=worlddomination.supervillain.org
   2. Review the DATABASE variables. You may want to substitute your own values for the default database names, user names and passwords.
   3. Turn on the new site-wide reporting functionality by adding the REPORTS_* variables. See Turn on site-wide reporting for details.
   4. If you don't specify a domain name, replace the HOST_localhost token with the hostname. Otherwise, ViewVC pages for Subversion and CVS repositories created after the site is up, will be rendered with a CSS error.
   5. Important: It is mandatory that you include the SCM_DEFAULT_SHARED_SECRET token in the site-options.conf file of the primary TeamForge server, and give it a value of 16-24 characters.
      Remember that you need to use that same key in the external SCM integration server also.
7. Run the installer.
   • cd /opt/collabnet/teamforge-installer/6.1.1.0
   • ./install.sh -r -I -V
8. Set up the initial site data.
   • ./bootstrap-data.sh
9. Start TeamForge.
   • /etc/init.d/collabnet start
10. Apply some finishing touches and make sure everything is running smoothly.
    1. Turn on SSL for your site by editing the relevant variables in the site-options.conf file. See Set up SSL for your TeamForge site.
    2. Reboot the server and make sure all services come up automatically at startup.
    3. On CentOS, Apache may not automatically start up after a reboot. To ensure that it does, run this command now:
       • /sbin/chkconfig --level 2345 httpd on
    4. Log into your site as the administrator. The value of the DOMAIN variable in the site-options.conf file is the URL to log into.
    5. Install a project template. TeamForge comes with a sample project template that showcases some of the platform's most interesting features. Site administrators and project managers can use this template to jump-start projects without a lot of manual setup steps. See Install project templates.
    6. Create a sample project. See Create a TeamForge project.
    7. Write a welcome message to your site's users. See Create a site-wide broadcast.