NOTE
StrongLoop Arc and slc are no longer under active development, and will soon be deprecated. Arc's features are being included in the IBM API Connect Developer Toolkit: Please use it instead.
Skip to end of metadata
Go to start of metadata

Run a Node application (including a LoopBack application) under control of StrongLoop PM to: 

For more information, see Using Process Manager.

Icon

The slc start command does not run on Windows systems. However, you can run StrongLoop PM on a Windows system and deploy to it. See Building and deploying for more information.

To run an app locally under control of StrongLoop Process Manager:

Where <app-root-dir> is the application's root directory.

This starts a local instance of StrongLoop Process Manager (StrongLoop PM) and runs the specified application under its control.  If PM is unable to start the application, it will periodically try to start the app until the PM is shut down.  

StrongLoop PM will display some suggested commands, followed by information from the log file, for example:

You can also run an application from another directory.  For example, if your application is in the myApp directory under the current working directory:

To run an application remotely, use Process Manager; see Operating Node applications for more information.

To view the status of the application, use the slc ctl command, which by default displays the status of the locally-running StrongLoop PM:

Where myapp is your application's service name (by default, the name property in package.json).

To see log output (including error messages and a stack trace), use this command:

Icon

If PM cannot successfully run the application, you can make changes to the application code, and PM will automatically try to run it: you don't have to use slc start again.

Stop the application with:

  • No labels