Customize your PostgreSQL configuration

The following instructions illustrate how you can include custom configuration to PostgreSQL and disable the same if not required.

  1. Create conf.d/pgsql/pg_hba.conf.d/ under /opt/collabnet/teamforge/etc/ directory.

    If the reporting service is running on a separate port, create conf.d/reports-pgsql/pg_hba.conf.d/ under /opt/collabnet/teamforge/etc/.

  2. Include custom.conf under /opt/collabnet/teamforge/etc/conf.d/pgsql/pg_hba.conf.d/.

    If the reporting service is running on a separate port, include custom.conf under /opt/collabnet/teamforge/etc/conf.d/reports-pgsql/pg_hba.conf.d/

  3. Deploy services.
    1. Move all backup files and folders including the error folder to /tmp.
      Note: This step is required to make sure that there are no backup files and folders present in /opt/collabnet/teamforge/var/james/var/mail/ to avoid any delay during provisioning.
      • cd /opt/collabnet/teamforge/var/james/var/mail/
      • mv * /tmp
    2. Run the TeamForge provision command.
      • /opt/collabnet/teamforge/bin/teamforge provision

    The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "Yes" or "No" to proceed. For more information, see The teamforge script.

The following warning message is displayed, which you can ignore.

Custom configuration found in /opt/collabnet/teamforge/etc/conf.d/pgsql/pg_hba.conf.d has been applied. Please be aware of that such configuration may impact the reliability of TeamForge.

If the reporting service is running on a separate port:

Custom configuration found in /opt/collabnet/teamforge/etc/conf.d/reports-pgsql/pg_hba.conf.d has been applied. Please be aware of that such configuration may impact the reliability of TeamForge.

Configuration settings from custom.conf are included in /var/lib/pgsql/9.3/data/pg_hba.conf.

If the reporting service is running on a separate port, configuration settings from custom.conf are included in /var/lib/pgsql/9.3/reports/pg_hba.conf.

  1. Check the postgresql.log file for any syntax errors: /opt/collabnet/teamforge/log/pgsql/postgresql.log.

Remove custom configuration

  1. To remove custom configuration:
    • cd /opt/collabnet/teamforge/etc/conf.d/
    • mv pgsql pgsql_old
    If the reporting service is running on a separate port:
    • cd /opt/collabnet/teamforge/etc/conf.d/
    • mv reports-pgsql reports-pgsql_old
  2. Deploy services.
    1. Move all backup files and folders including the error folder to /tmp.
      Note: This step is required to make sure that there are no backup files and folders present in /opt/collabnet/teamforge/var/james/var/mail/ to avoid any delay during provisioning.
      • cd /opt/collabnet/teamforge/var/james/var/mail/
      • mv * /tmp
    2. Run the TeamForge provision command.
      • /opt/collabnet/teamforge/bin/teamforge provision

    The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "Yes" or "No" to proceed. For more information, see The teamforge script.