Configuring

To edit the Linkurious Enterprise configuration, you can either edit the configuration file located at linkurious/data/config/production.json or use the Web user-interface:

Using an administrator account, access the Admin > Global configuration menu to edit the Linkurious Enterprise configuration:

Some configuration change requires a restart to be applied. Linkurious Enterprise will notify you about it and offer you to restart from the Web UI only if you made the changes from the Web UI itself. If you modified the production.json file manually, changes won't get applied immediately and you will need to restart Linkurious Enterprise.

Configuration keys are divided by category.

Password fields will always be hidden from the Web UI, but they can be edited.

Variable expansion

You can also pass variables to the configuration, that will in turn expand to their appropriate value from environment variables or files. For example using : $ENV:NEO4J_PASSWORD in the configuration will expand to the value of the environment variable NEO4j_PASSWORD.

Expandable variables are:

• $ENV:VAR1: replaced with the value of the process' environment variable called VAR1.
• $ENV-NUMBER:VAR2: replaced with the value of the process' environment variable called VAR2 parsed as a number.
• $ENV-JSON:VAR3: replaced with the value of the process' environment variable called VAR3 parsed as JSON.
• $FILE:/path/to/file: replaced with the content of the file at /path/to/file parsed as a UTF-8 string.

In the configuration object, you can use the following syntax:

When you are finished changing, click Save.

Limitation: There are some limitations with the "$ENV-JSON" expansion,

$ENV-JSON does not work when used at the root level or at the first level of the configuration (for example for the whole server.* configuration key.)

$ENV-JSON does not work when used at any level within the dataSource.* configuration key.