Configuration Files OverviewΒΆ

RhodeCode Enterprise and RhodeCode Control have a number of different configuration files. The following is a brief explanation of each, and links to their associated configuration sections.

- rhodecode.ini

Default location: /home/user/.rccontrol/instance-id/rhodecode.ini

This is the main RhodeCode Enterprise configuration file and controls much of its default behaviour. It is also used to configure certain customer settings. Here are some of the most common reasons to make changes to this file.

- mapping.ini

Default location: /home/user/.rccontrol/instance-id/mapping.ini

This file is used to control the RhodeCode Enterprise indexer. It comes configured to index your instance. To change the default configuration, see Advanced Indexing.

- vcsserver.ini

Default location: /home/user/.rccontrol/vcsserver-id/vcsserver.ini

The VCS Server handles the connection between your repositories and RhodeCode Enterprise. See the VCS Server Management section for configuration options and more detailed information.

- supervisord.ini

Default location: /home/user/.rccontrol/supervisor/supervisord.ini

RhodeCode Control uses Supervisor to monitor and manage installed instances of RhodeCode Enterprise and the VCS Server. RhodeCode Control will manage this file completely, unless you install RhodeCode Enterprise in self-managed mode. For more information, see the Supervisor Setup section.

- .rccontrol.ini

Default location: /home/user/.rccontrol.ini

This file contains the instances that RhodeCode Control starts at boot, which is all by default, but for more information, see the Manually Start At Boot section.

- .rhoderc

Default location: /home/user/.rhoderc

This file is used by the RhodeCode Enterprise API when accessing an instance from a remote machine. The API checks this file for connection and authentication details. For more details, see the Configure the .rhoderc File section.


Default location: /home/user/.rccontrol/cache/MANIFEST

RhodeCode Control uses this file to source the latest available builds from the secure RhodeCode download channels. The only reason to mess with this file is if you need to do an offline installation, see the Offline Installation instructions, otherwise RhodeCode Control will completely manage this file.