The following pages are either added or updated for TeamForge 19.1.
The following pages are tagged with
| Title | Excerpt |
|---|---|
| Install All Services on a Single RHEL/CentOS Server | The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings. |
| Install TeamForge with an External PostgreSQL Server | You can install TeamForge with its database installed separately on an external PostgreSQL server such as AWS RDS/Aurora. |
| Install TeamForge in a Distributed Setup | Distributed setup with TeamForge, Database (including Datamart), EventQ, Review Board, SCM (Subversion, CVS and Git), Code Search and Baseline installed on s... |
| domain_change_webr.py | The domain_change_webr.py script is used to change the domain name or host name of the subscriber in the Webhooks-based Event Broker database. |
| Install TeamForge with Oracle Database | Distributed setup with TeamForge, Oracle Database (including Datamart) and EventQ installed on separate servers. |
| Mass Configuration of Repository Policies Within a Project | You may often want to apply a specific set of policies to more than one repository. You can just select multiple repositories within a project and apply your... |
| Upgrade TeamForge on New Hardware with All Services on a Single Server | You can upgrade TeamForge on new hardware with all services on a single server. |
| Installation Requirements | Here's what it takes to install and run TeamForge, EventQ and other integrations supported by TeamForge. |
[]: