Upsource Launcher properties
The properties listed on this page are used by Upsource Launcher process and can be added or edited in the configuration file upsource.jvmoptions to change Upsource settings that are not available in the UI.
Upsource-specific properties
Upsource-specific properties in the table below can only be changed on a persistent basis with the configure command. See a corresponding step-by-step instruction for a ZIP or Docker installation.
| Property | Description | Type | Availability by installation type |
|---|---|---|---|
base-url | Base URL of Upsource. Defines the URL that end users will use to access your running Upsource services. Default value is either: "http://" + hostname + ":" + listen-port + "/" or "http://" + hostname + "/" (in case when listen-port is equal to 80) (where "hostName" is the name of the server Upsource is installed on) | string | ZIP and Docker |
listen-address | The default value is 0.0.0.0 It might be changed if Upsource should be configured to listen on some particular net interface. | string | ZIP and Docker |
listen-port | Port the Upsource process starts on. This port might be changed from one configuration phase to another. By default port 80 is tried to be used on Windows and 8080 on other platforms. Port 8080 and all subsequent ports are tried if Upsource could not start listening on port 80 (if it's occupied by another process or is not allowed). | int | ZIP and Docker |
backups-dir | The directory in which time-specific backup folders will be stored when created. The default value is <upsource_home>\backups. | string | ZIP and Docker |
statistics-upload | Permission from a user to collect and upload anonymous statistics about services. The default value is False. This property is normally set by the admin in Configuration Wizard. | boolean | ZIP and Docker |
Launcher default JVM options
The following JVM options are configured for the Upsource Launcher process by default. You can change their default values either on the persistent basis or temporarily (ad hoc).
See a corresponding step-by-step instruction for a ZIP or Docker installation.