Bootstrapping Helix TeamHub

The Helix TeamHub Admin is a simple UI application for configuring and managing Helix TeamHub configuration. Use the following steps to configure hostname and mail settings to your instance. To start, go to the /admin URL of the Helix TeamHub installation.

Step 1: Configure Hostname

In order to use Helix TeamHub, a valid host name is required. The Helix TeamHub hostname must be a fully qualified domain name (FQDN) and resolvable by product users. Helix TeamHub will use this configured hostname in repository URLs, email links, and API requests. Even though Helix TeamHub can be configured to use IP address or another hostname assigned to the server, a delegated alias (CNAME) or name (A) to simplify future server relocations is recommended.

The "Preferences" page provides a number of other configurations, such as: Authentication method, enabling Helix TeamHub LDAP interface, and enforcing SSL. However, the first step is to bootstrap Helix TeamHub to make sure everything works as expected. Enter the hostname and click "Save preferences".

Configuring hostname

Step 2: Setup Mail

Enter the Support email, which is used in all outgoing Helix TeamHub emails, as well as the links to the Support team throughout application. To configure external SMTP server for handling Helix TeamHub emails, see Mailing Configuration section.

Setting up mailing

Step 3: Apply Configuration Changes

While completing the previous steps, the following warning appears:

Reconfiguration warning

This warning occurs every time the configuration is changed in some way that affects underlying Helix TeamHub services. Simply log in to the server, and run the sudo hth-ctl reconfigure command to address this issue.

Note: For Cluster Deployment, apply the changes on every Helix TeamHub Web server.

Congratulations, the Helix TeamHub instance is successfully bootstrapped and ready to use. It's a good time to test everything and further extend Helix TeamHub for production use:

Updated on: 5 October 2017