Using the AppSettings Override File

The StifleR Server Configuration File contains multiple settings that are often modified and tweaked after the StifleR server is installed. Unless the file is backed up, these changes may be lost during an upgrade or re-installation. Even in the scenario in which the config file is backed up, it is not safe to restore it after an upgrade, because new .config settings may be introduced in newer versions.

To solve this issue, 2Pint has provided the option of using an AppSettings Override configuration file. This file can contain all of the settings which are stored in the StifleR config file and will essentially override them if the file is present. These settings will also override any settings defined when running the installation wizard except for the installation directory.

The file is read when the "2Pint Software StifleR Server" service starts.

The file must be named appSettings-override.xml and must be located in the StifleR Server installation folder. This file does not exist by default, and must be created by the administrator. The file will be preserved and will not be deleted during an uninstall, upgrade, or fresh installation.

The acceptable key values which can be added are documented on the StifleR Server Configuration File page.

The syntax of the file is as follows:

<?xml version="1.0" encoding="utf-8"?>
<!-- PUT THIS FILE IN THE BIN DIRECTORY OF THE SERVICE TO OVERRIDE SETTINGS WITHOUT EDITTING THE APP.CONFIG DIRECTLY -->
<appSettings>
  <add key="NewLocationDatabasePath" value="E:\2Pint_Data\StifleR\Server\Databases\Location" />
  <add key="MainDatabasePath" value="C:\ProgramData\2Pint Software\StifleR\Server\Databases\Main" />
  <add key="HistoryDatabasePath" value="C:\ProgramData\2Pint Software\StifleR\Server\Databases\History" />
  <add key="SignalRCertificateThumbprint" value="1234567890abcdef1234567890abcdefg1234567"/>
  <add key="WebServiceCertificateThumbprint" value="1234567890abcdef1234567890abcdefg1234567"/>
 </appSettings>

Last updated