sanboxruby — Command Reference
Manage a domain-specific Ruby sandbox and its application packages.
Manage a domain-specific Ruby 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/sanboxruby -i example.com RUNTIME_IDArguments and options
| Syntax | Meaning |
|---|---|
-i, --install, install DOMAIN RUBY | Create a Ruby sandbox. |
-id, --installdemo DOMAIN RUBY | Create a sandbox and demo Rails application. |
-r, --remove, remove, del DOMAIN | Delete the domain sandbox. |
-ri, --reinstall, reinstall DOMAIN | Reinstall its configured sandbox. |
-gs, gem_setup DOMAIN ACTION GEMS | Perform a gem action; gem 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 -gs DOMAIN ACTION GEMS, use install, update or uninstall as the action and a comma-separated gem list. The current handler treats every action other than install or update as uninstall. The uninstall path forces removal and ignores dependencies, so check the action and dependent applications carefully.
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.