The easiest way to adapt jsreport to your needs is to change its configuration. jsreport configuration provides many options like changing http port, setting store provider to different mechanism and many others.
Hint:You can get the list of supported configuration options using command
jsreport help config
jsreport merges configuration from config file, environment variables, command line arguments and also directly from the application code in this exact order.
The configuration file is the most common way to adapt jsreport. The default jsreport.config.json is usually pre-created for you if you follow installation instructions.
jsreport also loads dev.config.json or prod.config.json based on the NODE_ENV=development or NODE_ENV=production environment variable if such file exists.
The config file can be also explicitly specified using configFile=path option which can be passed from one of the configuration source methods. The config file path can be both relative or absolute.
Hint: You should see the currently applied configuration file name in the first lines of log when starting the instance.
info: Initializing jsreport@2.0.0 in development mode using configuration file: jsreport.config.json
The environment variables are collected and merged into the final configuration during the jsreport startup as well. You can use it to change the port for example:
unix:
httpPort=3000 jsreport start
windows:
set httpPort=3000&&jsreport start
This will start jsreport on port 3000 even if you have the httpPort entry in the config file because the environment variables have the higher priority.
If you want to use environment variable for configuring a complex object you should separate the nested path in the key using _ :
unix:
extensions_authentication_admin_username=john jsreport start
windows:
set extensions_authentication_admin_username=john
jsreport start
another alternative to the _ separator is to use the : as separator
unix:
env extensions:authentication:admin:username=john jsreport start
windows:
set extensions:authentication:admin:username=john
jsreport start
The command line arguments are parsed as well. This is very convenient for changing the port for example:
jsreport start --httpPort=3000
The configuration for complex objects should use the . as separator
jsreport start --extensions.authentication.admin.username=john
The last option is to edit the server.js file which is part of the default installation. This is usually common when integrating jsreport into existing node.js application. Note this approach cannot be used if you use precompiled jsreport binary.
const jsreport = require('jsreport')({
httpPort: 3000
})
Each extension (recipe, store...) usually provides some options you can apply and adapt its behavior. These options can be typically set through standard configuration under the top level extensions property, in which you can put the specific extensions options with extension's name inside it. For example the authentication can be configured under the same named node in the config.
"extensions": {
"authentication": {
"admin": {
"username" : "admin",
"password": "password"
}
}
}
extensions that has a name with a hyphen in it (like html-to-xlsx for example) also supports receiving configuration with the name in camel case, so both of the following examples are valid for extensions with hyphen in its name
"extensions": {
"html-to-xlsx": {
...
}
}
"extensions": {
"htmlToXlsx": {
...
}
}
This support of camel case form of extensions also works when specifying configuration as cli arguments or env vars, which is handy when working in environments where is difficult to pass arguments or env vars with hyphens.
jsreport start --extensions.htmlToXlsx.someConfig value
extensions_htmlToXlsx_someConfig=value jsreport start
Please refer to particular extension's documentation to find what configuration options you have. There is usually Configuration section where you can find it.
You can disable an extension by setting enabled: false in the configuration of particular extension. You can for example disable jsreport studio, API and authentication using this config.
{
"extensions": {
"authentication": {
"enabled": false
},
"studio": {
"enabled": false
},
"express": {
"enabled": false
}
}
}
httpPort (number) - http port on which is jsreport running, if both httpPort and httpsPort are specified, jsreport will automaticaly create http redirects
from http to https, if any of httpPort and httpsPort is specified default process.env.PORT will be used
httpsPort (number) - https port on which jsreport is running
certificate object - path to key and cert file used by https
"certificate": {
"key": "certificates/jsreport.net.key",
"cert": "certificates/jsreport.net.cert"
}
or if your certificate is a .pfx file then you can use the pfx and passphrase options
"certificate": {
"pfx": "certificates/jsreport.net.pfx",
"passphrase": "<if pfx file is protected specify the password here>"
}
hostname (string) - hostname to be used for the jsreport server (optional)
extensions.express.inputRequestLimit (string) - optional limit for incoming request size, default is 2mb
appPath (string) - optionally set application path, if you run application on http://appdomain.com/reporting then set "/reporting" to appPath. The default behavior is that it is assumed that jsreport is running behind a proxy, so you need to do url url rewrite /reporting -> / to make it work correctly, See mountOnAppPath when there is no proxy + url rewrite involved in your setup.
mountOnAppPath (boolean) - use this option along with appPath. it specifies if all jsreport routes should be available with appPath as prefix, therefore making appPath the new root url of application
store (object) - jsreport supports multiple implementations for storing templates. The particular implementation is distinguish based on store.provider attribute. The predefined value in the precreated configuration file is fs which employs jsreport-fs-store to store report templates on the file system. Alternatively you can install additional extension providing template store and change store to reflect it. You can find the list of available store drivers and further details how to configure them here.
blobStorage (object) - optional, specifies type of storage used for storing reports. The particular implementation is distinguish based on blobStorage.provider attribute. It can be fs, memory or gridFS. Defaults to fs in full jsreport or to memory when integrating jsreport into existing node.js application.
rootDirectory (string) - optionally specifies where's the application root and where jsreport searches for extensions
tempDirectory (string) - optionally specifies absolute or relative path to directory where the application stores temporary files
configFile (string) - relative or absolute path to the configuration json file to be used
allowLocalFilesAccess (boolean) - When true this property specifies that jsreport should allow access to the local file system and use of custom nodejs modules during rendering execution
reportTimeout (number) - total timeout in ms for a one report rendering
Until jsreport reaches version 3.0.0, there are also granular options for timeout like templatingEngines.timeout or chrome.timeout supported. However, these are deprecated and just reportTimeout should be used. Both reportTimeout and granular options don't work together and in case both are filled in the configuration, just reportTimeout is applied. There is currently no default for reportTimeout because of back-compatibility. If it isn't filled, the granular timeouts are used.
enableRequestReportTimeout (boolean) - opt in for leting rendering requests use options.timeout to override general reportTimeout configuration
jsreport uses by default dedicated processes for rendering pdf or scripts. This solution has higher level of isolation. However you can get better performance when configuring jsreport to reuse processes.
"chrome": {
"strategy": "chrome-pool"
},
"templatingEngines": {
"strategy": "http-server"
}
templatingEngines (object) - this attribute is optional and is used to configure the component that executes rendering tasks. This component is used to execute javascript templating engines during rendering or in scripts extension.
templatingEngines.strategy (dedicated-process | http-server | in-process) - The first strategy uses a new nodejs instance for every task. The second strategy reuses every instance over multiple requests. Where http-server has better performance, the default dedicated-process is more suitable to some cloud and corporate environments with proxies. The last in-process strategy simply runs the scripts and helpers inside the same process. This is the fastest, but it is not safe to use this strategy with users' templates which can have potentially endless loops or other critical errors which could terminate the application. The in-process strategy is also handy when you need to debug jsreport with node.js debugging tools.
templatingEngines.numberOfWorkers (number) - how many child nodejs instances will be used for task execution
templatingEngines.host (string) - Set a custom hostname on which script execution server is started, useful is cloud environments where you need to set specific IP.
templatingEngines.portLeftBoundary (number) - set a specific port range for script execution server
templatingEngines.portRightBoundary (number) - set a specific port range for script execution server
templatingEngines.allowedModules (array) - set the allowed external modules that can be used (imported with require) inside helpers of template engines. Ex: allowedModules: ["lodash", "request"], alternatively you can enable importing any external module using allowedModules: "*". If instead of helpers you want to control the allowed modules for scripts then check the corresponding docs
jsreport core provides general functions for encrypting/decrypting sensitive data like passwords or certificates. The extensions like pdf-sign or office-password then use this API.
encryption.secretKey (string) - must be exactly 16 chars long string
encryption.enabled (boolean) - the encryption can be disabled this way
Note: Logging in jsreport is implemented using the winston package and many of its concepts apply the same for jsreport logging configuration
logger (object) - To have complete control about logging in jsreport you can declare output (where should logs be sent) and log level using an object:
{
"logger": {
"console": { "transport": "console", "level": "debug" },
"file": { "transport": "file", "level": "info", "filename": "logs/log.txt" },
"error": { "transport": "file", "level": "error", "filename": "logs/error.txt" }
}
}
For example the above config specifies the following:
configure an output named "console" which sent all logs with level debug, and all levels with low priority than debug level ("level": "debug") to the console ("transport": "console")
configure and output named "file" which sent all logs with level info, and all levels with low priority than info level ("level": "info") to the file system ("transport": "file") storing them at "logs/log.txt" ("filename": "logs/log.txt")
configure and output named "error" which sent all logs with level error, and all levels with low priority than error level ("level": "error") to the file system ("transport": "file") storing them at "logs/error.txt" ("filename": "logs/error.txt")
Each output object specifies where to send the logs using a transport property and which is the level that should taken in consideration using a level property.
As you can see in the previous logging configuration each output object can take additional properties that let you configure the functionality of a transport, for example in the case of the output named "file", we are using the filename property to tell the file transport where to save the logs, each transport type supports a different set of properties to configure its behaviour.
Values for the transport property:
debug -> specifies that logs should be sent to console but they only be visible when using DEBUG=jsreport env varconsole -> specifies that logs should be sent to console, available options herefile -> specifies that logs should be sent to the file system, available options herehttp -> specifies that logs should be sent to and http endpoint, available options hereAvailable log level ordered by priority (top ones have more priority):
sillydebugverboseinfowarnerrorFor advanced use cases we provide a way to configure output which can use a transport available from external modules using the module property, since logging in jsreport is implemented using the winston package any external module that is compatible with winston transports will work in jsreport, for example to tell jsreport to use the third-party winston-loggly transport you can create a configuration like the following:
{
"logger": {
"loggly": {
"module": "winston-loggly", // module should be the name of the third-party module
"transport": "Loggly",
"level": "info",
// custom loggly transport options, see https://github.com/winstonjs/winston-loggly
"subdomain": "test",
"inputToken": "<your token here>",
"auth": {
"username": "<your-username>",
"password": "<your-password>"
}
}
}
}
Default logger configuration in jsreport:
{
"logger": {
"debug": {
"transport": "debug",
"level": "debug"
},
"console": {
"transport": "console",
"level": "debug" // "info" in production mode
},
"file": {
"transport": "file",
"level": "debug" // "info" in production mode
},
"error": {
"transport": "file",
"level": "error"
}
}
}
Note that you can override all or just some part of the predefined configuration using:
{
"logger": {
"console": {
"level": "error" // now only logs with level "error" will be sent to console, the rest of predefined outputs are still configured, we are only overriding the "level" option for the predefined console output here
}
}
}
Special options:
boolean): handy option to silence (logs will not be stored) all outputs configured. default: false{
"store": { "provider": "fs" },
"httpPort": 3000,
"allowLocalFilesAccess": true,
"blobStorage": { "provider": "fs" },
"reportTimeout": 60000,
"logger": {
"console": {
"transport": "console",
"level": "debug"
},
"file": {
"transport": "file",
"level": "info",
"filename": "logs/reporter.log"
},
"error": {
"transport": "file",
"level": "error",
"filename": "logs/error.log"
}
},
"templatingEngines": {
"numberOfWorkers" : 2,
"strategy": "http-server"
},
"extensions": {
"authentication" : {
"cookieSession": {
"secret": "dasd321as56d1sd5s61vdv32"
},
"admin": {
"username": "admin",
"password": "password"
}
}
}
}