HOST_localhost

The HOST variable identifies which of the TeamForge site's services are to run on a given machine.

Values

One or more of: app, database, cvs, subversion, etl, datamart

Default

app database cvs subversion etl datamart

Comments

Multiple applications can be assigned to a host. List the applications in space-separated format.

Important:

app (the main TeamForge application) must be assigned to one host only.
database (the PostgreSQL or Oracle application) must be assigned to one host only.

Examples

Here are some possible variations on the HOST_ variable when configured on the box where the main TeamForge application is running.

This host has been assigned the main application, the database, and the Subversion and CVS source control services:
```
HOST_localhost=app database subversion cvs
```

This is a two-box setup with a database running on a separate machine:

HOST_localhost.example.com=app subversion cvs etl datamart
HOST_mydatabase.mydomain.net=database

This is a three-box setup with Perforce and the TeamForge application running on one machine, the database on another and the reporting services on a third:
```
HOST_localhost=app perforce
HOST_mydatabase.mydomain.net=database
HOST_myreportingbox.mydomain.net=etl datamart
```
This is a three-box setup with the TeamForge application and reporting engine on one machine, both databases on another machine, and the source control services on a third machine.
```
HOST_localhost=app etl
HOST_mydatabase.mydomain.net=database datamart
```

This is a four-box setup:

HOST_localhost.com=app database
HOST_myreportingbox.mydomain.net=etl datamart
HOST_mycvs.mydomain.net=cvs

Note: Observe that when the source control integrations run on a separate box from the main application, no HOST_ variable is needed on the application box to point to the source control box. The source control machine needs to know how to find the main application box, but the application box does not need to know where the source code integration box is.