Skip to main content

Installing plugins (legacy)

The plugin installation process for Informer 2025.2.12 and earlier. For 2025.2.13 and later, see Installing plugins.

Check compatibility first

Before installing any plugin, contact Support at i5support@entrinsik.com to verify compatibility with your target Informer version.

Windows​

Stop the Informer service and any Node.js processes still running. Then open an elevated PowerShell window and change to the Informer installation directory (for example, C:\Entrinsik\Informer5).

Delete the lock file first

Delete package-lock.json if it exists in the top level of the Informer installation folder before continuing.

The first time you install a plugin, log in to the repository (contact Support for credentials):

npm config set registry https://docker.entrinsik.com/repository/npm/
npm adduser --registry https://docker.entrinsik.com/repository/npm/

When prompted, enter the credentials Support provided. Then configure and install the plugin:

informer plugin <plugin name>
npm install <plugin name> --save

An example plugin name is @entrinsik/salesforce.

To install a specific plugin version, add it to the npm install command, replacing x.y.z with the version:

npm install <plugin name>@x.y.z --save

Afterward, there may be additional details to set in config.json, as described in the plugin's documentation.

Linux (Docker)​

Edit config.json, add the block below, and restart Informer:

"plugins": {
  "<plugin name>": {}
}

For example, to add the Salesforce plugin:

"plugins": {
  "@entrinsik/salesforce": {}
}
Pinning a plugin version on Docker

To install a specific plugin version on a Docker deployment, contact Support for the correct config.json configuration for your Informer version.

NPM user passthrough for custom plugins (legacy path)​

This is not a common case; follow these steps only if Support directs you to. When a custom commissioned plugin needs repository access the default Informer user does not have, you can pass the host's npm credentials through to the containers by mounting the host .npmrc file.

On these legacy versions, the container-side path is /root/.npmrc. Log in to the server as the maintenance user (this example uses administrator), find that user's .npmrc (by default in their home directory, for example /home/administrator/.npmrc), and add the volume mount to each Informer container in docker-compose.yml:

informer-schedules:
  image: docker.entrinsik.com:5000/informer:target
  working_dir: /informer
  entrypoint: "/bin/sh -c 'node dockerpreboot.js && pm2 start index.js -i 2 --name informer --no-daemon'"
  volumes:
    - ./plugins:/informer/plugins
    - ./java/plugins:/informer/java/plugins
    - ./config.json:/informer/config.json
    - /home/administrator/.npmrc:/root/.npmrc

Save the changes, then stop and start Informer to apply them. The host's npm credentials now replace the container's defaults, so custom plugins that require special access become reachable.

On 2025.2.13 and later

The container-side path changed to /informer/.npmrc. See Custom NPM user for plugin access for the current process and the upgrade path.