The `node-red-admin` package provides a command-line interface for remote administration of Node-RED instances. It enables users to perform various management tasks such as listing, enabling, disabling, installing, and removing Node-RED nodes, setting target Node-RED instances, authenticating users, and generating hashed passwords for `adminAuth` configuration. The current stable version is 4.1.5, with frequent patch and minor releases, and major versions typically update Node.js compatibility and introduce core changes. It can be installed globally as a standalone tool or is bundled and available when `node-red` itself is installed. Its primary differentiator is offering a robust, scriptable interface for managing Node-RED environments without needing direct access to the Node-RED editor UI, making it invaluable for automation and deployment workflows.
npm install node-red-adminNo compatibility data collected yet for this library.
Demonstrates global installation and common command-line usages of the Node-RED Admin CLI, including setting targets, logging in, listing nodes, and hashing passwords.
Upgrade your Node.js installation to version 18 or newer. Use `nvm` or `fnm` for managing multiple Node.js versions: `nvm install 18 && nvm use 18`.
Use `sudo npm install -g node-red-admin` (for macOS/Linux) or `npm install -g node-red-admin --unsafe-perm` if `sudo` is not desired or causes issues. Alternatively, configure npm to install packages in a user-owned directory.
Review Node-RED V3 migration guides for any `httpStatic` or related configuration changes. Ensure your Node-RED instance is compatible with the version administered by `node-red-admin`.
Regularly update `node-red-admin` to the latest stable version to ensure all security patches are applied: `npm install -g node-red-admin@latest`.
Use the `--userDir DIR` argument with any `node-red-admin` command to specify an alternative directory for the configuration file, allowing for isolated or custom configurations.
Run `npm install -g node-red-admin` with elevated privileges using `sudo` (e.g., `sudo npm install -g node-red-admin`) or configure npm to use a user-owned directory.
Ensure `npm install -g node-red-admin` completed successfully. Verify that your npm global binaries directory is included in your system's PATH environment variable (e.g., `~/.npm-global/bin` or `/usr/local/bin`).
Update your Node.js runtime to version 18 or higher. Consider using a Node.js version manager like `nvm` (`nvm install 18 && nvm use 18`) or `fnm`.
Ensure your Node-RED instance is running. Verify that `node-red-admin target <your-node-red-url>` is correctly set and that there are no firewall or network issues blocking access to the Node-RED admin API port.