Configure BladeRunner

This page describes some of the areas that you can configure within BladeRunner.

Logging

When you start BladeRunner, you can set a logging level to control. By default, BladeRunner writes basic informational messages to standard output. You can have more detailed messages written by adding the --verbose or --debug (most detailed) flags as shown below:

  • bladerunner start --verbose

  • bladerunner start --debug


Ports

Within the BladeRunner installation directory, navigate to the conf directory. Within this directory, open the file bladerunner.conf in a text editor.

Locate the property jettyPort, and edit the port number as required.

Input encoding

Within the BladeRunner installation directory, navigate to the conf directory. Within this directory, open the file bladerunner.conf in a text editor.

Locate the property defaultInputEncoding, and edit the default encoding as required.

Compression levels

Within the BladeRunner installation directory, navigate to the conf directory. Within this directory, open the file bladerunner.conf in a text editor.

Locate the minifiers section. This contains a list of available minification (compression) levels for when you produce your war file. To generate a war file that is compressed using Google Closure "simple minification", use the following command:

bladerunner war -m closure-simple

Browser test configurations

Within the BladeRunner installation directory, navigate to the conf directory. Within this directory, open the file test-runner.conf in a text editor.

Follow the instructions in this file to specify the configuration for the js-test-driver server and the browsers that are used when you run tests.

Logins and roles (Caplin Trader)

Within the BladeRunner installation directory, navigate to the conf directory. Within this directory, open the file users.properties in a text editor.

Within this file you will find Caplin Trader user credentials.