DOCUMENTATION

From rPath Wiki

rBuilder users can be in development teams with several projects covering multiple repositories. One deployment consideration is managing the mappings between the hostname part of a project's label and that project's networked repository, called repository maps.

Part of Conary configuration for each appliance development environment is a repositoryMap directive to match the project label to the project repository. In the configuration, each context has its own repositoryMap value, and appliance developers configure one or more contexts for each rBuilder project on which they develop. As projects are created, more repositoryMap lines must be added to this file, increasing the possibility of incorrect or outdated mappings.

To simplify the management of these repository maps, rBuilder automatically maintains a list of repositoryMap lines. This includes one line for each internal project and one line for each external project with inbound mirror attached. rBuilder serves this list at http://<hostname>/conaryrc where <hostname> is the host name of the rBuilder.

Appliance developers can add the following line to their configuration files to prompt Conary to update the repositoryMap lines to match an rBuilder:

includeConfigFile   http://<hostname>/conaryrc

Browse to the URL in a web browser to see the content that will be inserted into the Conary configuration. When new projects are created, the information from the URL is automatically updated.

For more information on enabling the includeConfigFile directive and using it to manage repository maps, see the Configure Repository Maps FAQ page at wiki.rpath.com.