StrongLoop Command Line Tools
slc is the command shell for the StrongLoop Process Manager, strong-pm, and
the LoopBack framework.
It includes both a CLI and a GUI.
For more details, see http://strong-pm.io and http://loopback.io.
It can be installed with:
npm install -g strongloop
usage: slc <-h|--help|-v|--version>usage: slc <command> [--help] [...]Command-line tool for development and control of a Node application.Options:-h,--help Print usage for slc, or for an slc command, and exit.-v,--version Print versions of slc and its dependencies, and exit.Commands:arc: StrongLoop GUI, an alternative to the CLILaunch the StrongLoop GUI, a graphical alternative to the `loopback`,`build`, `deploy`, and `pmctl` commands, that also offers run-timeprofiling and debugging.loopback: LoopBack application scaffolderCreate LoopBack 2.x applications, datasources, models, ACLs, and relations.debug: Node.js application debuggerstart: start a node application under a local process managerStart a local process manager, if necessary, and run the applicationin-place.build: package a node application for deploymentPackages a node application as an npm tarball or into a git deploy branch.Deploy the package using the `deploy` command, or your existing DevOpspipeline.deploy: deploy a node application packageDeploy an application to the StrongLoop process manager (see `pm-install`command), or to any PaaS that can accept a `git push` of a nodeapplication.ctl: control a node application hosted by the process managerRun-time remote control of clustering, profiling, logging, restart, etc.See the `pm-install` and `pm` commands.pm-install: install the StrongLoop process managerThe process manager hosts applications, allowing them to be deployed,re-deployed, controlled, and monitored, and for application metrics andlogs to be viewed in Arc and published to thirdparty services (Splunk,Datadog, Statsd, etc.). To experiment locally with the manager withoutinstalling, see the `pm` command.strongops: save StrongOps API key into strongloop.jsonA key is required to publish metrics to the StrongOps hosted service.These commands are used internally, and may be useful when building customtooling and integrations with StrongLoop features:pm: run the StrongLoop process managerNormally, the process manager is installed as a system service (upstart orsystemd) and run by the system, but it can be run directly forexperimentation, or to build custom DevOps deployment tooling.run: supervise a node applicationThe StrongLoop kernel, the supervisor extends a node application withnode clustering, profiling, metrics collection and delivery, dynamicprofiling, logging, etc. Normally, its used by the process manager, butit can be run directly for experimentation, or to build custom DevOpsdeployment tooling.runctl: control a node application hosted by the supervisorUseful when using the `run` command directly.registry: npm registry manipulationSwitch between npm registries and promote packages between them. Usefulas a component of DevOps/CI pipelines, or from the command line.
strongloop uses a dual license model.