Advanced Upsource tuning
Upsource settings that are not available in the UI can be configured using Upsource system properties. An Upsource instance consists of a number of services which are organized to run in three different processes:
|Upsource Launcher process||Upsource Frontend process||Upsource Cassandra process|
| || || |
There are three configuration files associated with Upsource processes, where system properties for each process are stored accordingly.
When you want to change settings for a particular process, refer to the table below to choose a correct configuration file and the properties to edit.
|Process||Configuration file name||Configuration file location||Command|
- Upsource Launcher properties let you manage administrative settings, such as base URL or port number. Some of these properties correspond to the system settings that can be set in the UI during the installation, but can only be changed programmatically with the
configurecommand. For a list of configurable Upsource Launcher properties, see Upsource Launcher properties.
- Upsource Frontend properties let you manage Upsource-specific settings that affect user experience, such as frequency of notification emails or max file size that can be displayed. Most of these settings are not available in the UI — they can be set programmatically with the
configurecommand or by manually editing the configuration file. For a list of configurable Upsource Frontend properties, see Upsource Frontend properties
- Upsource Cassandra properties let you manage JVM settings that can be changed to improve the Cassandra database (included with Upsource) performance. See Upsource Cassandra properties
For each process, there is also a number of JVM properties that let you manage behavioral, garbage collection, performance, and debugging settings of that process. These settings are not visible in the UI — they can only be changed programmatically with the
configurecommand or by manually editing the configuration file.
JVM options for the Upsource Launcher process can be also changed temporarily (ad hoc), for the current run only, with the
The command syntax varies depending on your Upsource installation type: ZIP or Docker.
For detailed syntax description and examples refer to the instruction that corresponds to your installation type: