TeamForge System Administration

You can follow these useful best practices for your TeamForge install and upgrade procedures.

Install project templates manually
Provide sample projects to help users get started quickly.
Install project templates using the installer
With TeamForge 17.11, you can install project templates automatically.
Set up an Oracle database
To use an Oracle database for your TeamForge data, set up the Oracle database and tell the installer how to handle it.
Change the scmviewer password
It is recommended to change the scmviewer password after installing TeamForge.
Install Memcached
Memcached caches Subversion (SVN) authentication and authorization information and serves the mod_authnz_ctf module's authentication and authorization requests thereby reducing the number of SOAP calls, which in turn results in less load on the TeamForge Application Server.
Upgrade on new hardware: Create a single cluster for both Database and Datamart
The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server is being deprecated in TeamForge 17.11. If you have the TeamForge database and datamart on separate PostgreSQL instances on the same server and if you are upgrading on a new hardware, follow these instructions to create a dump of both the database and datamart and load them into one PostgreSQL instance on the same server.
Synchronize TeamForge source control integrations
Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code.
Customize your Apache configuration
The following instructions illustrate how you can include custom configuration to Apache and disable the same if not required.
Customize your PostgreSQL configuration
The following instructions illustrate how you can include custom configuration to PostgreSQL and disable the same if not required.

Parent topic: Maintain your TeamForge 17.11 site