Set up SELinux

If SELinux is active on the machine where your CollabNet TeamForge site is running, modify it to allow the services that TeamForge requires.

1. Enable Apache (running on port 80) to proxy traffic to JBoss (running on port 8080).
   • setsebool -P httpd_can_network_connect 1
2. When you are installing TeamForge, follow these steps to enable services to come up when needed.
   1. Change the context for the TeamForge log.
      • chcon -R -h -t httpd_sys_content_t /opt/collabnet/teamforge/log/httpd
   2. Change the context for PostgreSQL.
      • chcon -R -h -t postgresql_db_t /var/lib/pgsql
   3. Create the PostgreSQL log directory and set the appropriate permissions.
      • mkdir /opt/collabnet/teamforge/log/pgsql
      • chown -R postgres:postgres /opt/collabnet/teamforge/log/pgsql
      • chmod 777 /opt/collabnet/teamforge/log/pgsql/
   4. Change the context for the PostgreSQL log.
      • chcon -R -h -t postgresql_db_t /opt/collabnet/teamforge/log/pgsql/
3. After your site is installed and contains some live data, follow these steps to allow source control services to work.
   1. Change the context for your Subversion source code service.
      • chcon -R -h -t httpd_sys_content_t /svnroot
   2. Change the context of the Subversion repository that handles the branding (look and feel) of your site.
      • chcon -R -h -t httpd_sys_content_t /sf-svnroot
      • chcon -R -h -t httpd_sys_content_t /opt/collabnet/teamforge/var/overrides
   3. Change the context for your local CVS repository, if you have one.
      • chcon -R -h -t httpd_sys_content_t /cvsroot