The configuration options for BladeRunnerJS and the built-in Jetty server, located within
conf/brjs.conf, are as follows:
jettyPort: The port the built in Jetty server will bind to (
defaultFileCharacterEncoding: The input encoding for files read by BRJS (
ignoredPaths: The list of paths that should be ignored when exporting via the
.svn, .gitby default).
loginRealm: The login realm the Jetty server will use — only needed if you configure a login realm within
useNodeCommands: Whether the Node.js versions of tools should be used in preference to the Rhino versions (
allowAnonymousStats: Whether anonymous usage statistics can be made available centrally to help improve BRJS (undefined by default).
The test specific configuration options for BladeRunnerJS, located within
conf/test-runner.conf, are as follows:
jsTestDriverJar: The path to the location of the
JsTestDriver.jarwithin the SDK.
portNumber: The port number of the test server (
defaultBrowser: The name of the browser to use if one isn't specified on the command-line (
browserPaths: A set of browser paths for different browsers, grouped by operating system.
conf/users.properties file contains a list of usernames, passwords & roles for those using the
loginRealm to enable authentication for their app. The file has entries having the form:
The configuration options for BladeRunnerJS apps, located within
apps/<app>/app.conf, are as follows:
requirePrefix: The require prefix for resources within the app (
locales: The comma delimited list of locales (e.g.
en, en_GB, de) supported by this app (
localeCookieName: The name of the cookie used to store the active locale (
BladeRunnerJS uses the Jetty J2EE application server to serve applications stored within the
apps/<app> directories. Apps that don't contain a
WEB-INF directory of their own (as required by J2EE servers) are programmatically configured to use centrally held configuration within the SDK. Apps that would like to have a
WEB-INF directory can use the
j2eeify command to create one, and are then free to customize
WEB-INF/web.xml with any app specific servlets or servlet-filters, etc.
web.xml deployment descriptor, located at
apps/<app>/WEB-INF/web.xml, contains the instructions necesarry to configure any J2EE server the app is deployed to — please see The Deployment Descriptor: web.xml for more information.
web.xml file is filtered during the
build-app process, allowing us to have different configuration in development and production. Development only configuration can be placed between
<!-- start-env: dev --> and
<!-- end-env --> tags, while production only configuration can be placed between
<!-- start-env: prod and
end-env --> tags, for example:
<!-- start-env: dev --> dev only xml here... <!-- end-env --> <!-- start-env: prod prod only xml here... end-env -->
The configuration within
jetty-env.xml is used to configure the Jetty server, and to provide any JNDI tokens required by the app. Unlike, the
jetty-env.xml isn't filtered during
build-app, as you will normally deploy to some other J2EE server in production, which you are responsible for configuring as appropriate. For more information on how to configure this file, please see jetty-env.xml.
.js-style file. Each
.js-style file contains either the text
common-js or the text
namespaced-js, and nothing else.