8 docs tagged with "site-options.conf"

Use the Configure Application tool to define your site level TeamForge settings.

This is the sample application-policy block that you can copy into your login-config.xml file to support LDAP authentication.

The pebble-app.xml file, also known as the Pebble application configuration file, contains the text that the Pebble application displays in the TeamForge user interface.

The pebble-dep.xml file, also known as the Pebble deployment configuration file, contains the data that Pebble needs to interact with the TeamForge site.

Change log of site-options.conf tokens.

Use the host:SERVICES and the host:PUBLIC_FQDN tokens to define the services and domain names of your TeamForge site respectively. You can also have unique service-specific FQDNs for services such as Subversion, Git, mail, Codesearch and so on.

Here's a list of TeamForge `site-options.conf` tokens and configuration information.

Use the teamforge.py script to deploy and undeploy services, start and stop services, verify the status of services, verify the application environment, bootstrap or migrate data, back up and restore data and do much more.