Skip to Content
Browse documentation

sanboxnodejs — Command Reference

Manage a domain-specific Node.js sandbox and its application packages.

Manage a domain-specific Node.js sandbox and its application packages.

Requirements

Run as root on the Eenos server. An existing domain with valid account ownership and an installed compatible Eenos runtime. Replace RUNTIME_ID with an identifier from the corresponding setup tool. Preserve the installed sanbox spelling.

Usage

The following example uses the operation described below; replace example identities and paths before use:

/usr/local/eenos/scripts/sanboxnodejs -i example.com RUNTIME_ID

Arguments and options

SyntaxMeaning
-i, --install, install DOMAIN NODEJSCreate a domain sandbox with the selected installed runtime.
-r, --remove, remove, del DOMAINDelete the domain sandbox.
-ri, --reinstall, reinstall DOMAINReinstall its configured sandbox.
-ns, npm_setup DOMAIN ACTION PACKAGESPerform an NPM action; the package expression is one argument.

This uses a positional/legacy parser. Choose one operation and keep its value order. Do not assume argparse-style --option=value, option combinations or --help support.

Operational effects

For -ns DOMAIN ACTION PACKAGES, use install, update or uninstall as the action and a comma-separated package list such as express,dotenv. The current handler treats every action other than install or update as uninstall, so an action typo can remove packages.

Creates, reinstalls or removes a domain environment and can install/remove application dependencies. Removal deletes the sandbox directory; preserve application data and dependency definitions before removing or reinstalling.

Pass a package list as one shell argument when the interface expects one value. Use trusted package names and simple domain/runtime identifiers; these legacy helpers assemble shell commands. Review dependency compatibility before upgrades.

Verify the result

Verify the domain environment, dependencies and application behavior after the operation.

Check operation output and the relevant service/application state. Several legacy wrappers exit successfully after logging a handler failure, so a zero shell exit status alone is not proof of completion.

Back to Runtimes & Sandboxes · All command-line tools