slc pm

After packaging an application with slc build, use slc deploy to deploy your application to the Process Manager.  See Building and deploying and Using Process Manager for more information.

To control Process Manager via HTTP, start it with the --control option and specify the desired port.  Then you can deploy apps to the PM using slc deploy , specifying the host name and port; and you can control PM using slc ctl.  To secure access to PM, enable HTTP basic authentication; see Securing Process Manager for more information.

SYNOPSIS

OPTIONS

-b, --base <basedir>
Save applications to basedir, including both Git repositories and npm packages, as well as the working directories, and any other files required.  Default  is .strong-pm in the current user's home directory (~/.strong-pm).  

-C, --control <ctl>
Listen for control messages on <ctl>.  Default is ctl.

-d, --driver <driver>  
Specify application execution driver, either direct (the default) or docker.

-l, --listen <port> 
Listen on <port> for application deployment and control commands.

--no-control
Do not listen for control messages.

-P, --base-port <port> 
Run applications on port number <port> + service ID.  Default base port is 3000.

STANDARD OPTIONS

-h, --help
Display help information.

-v, --version
Display version number.

EXAMPLE

Run StrongLoop Process Manager, listening on port 777:

Clone and push an application for a non-production deploy:

This brief example installed all the dependencies on the server.  In practice, build in app dependencies.  Do not install them dynamically at run-time; for example: