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

You can use StrongLoop Process Manager to manage any Node application, not just LoopBack applications.


You can use slc to build and package an application and then deploy to StrongLoop Process Manager:

  1. Run the StrongLoop Process Manager on the target deployment system.  See Using Process Manager.
  2. Use slc build to install and bundle an application's Node dependencies and create a deployable package.  See Building applications with slc and Installing dependencies for more details.
  3. Use slc deploy to deploy the application locally for testing or to a remote server for staging or production.  See Deploying apps to Process Manager.

Zero-downtime updates

StrongLoop Process Manager enables zero-downtime application updates.  You can roll out updates to a live application without having to halt it.

When you push an application update with slc deploy, Process Manager shuts down workers one at a time, while simultaneously bringing up the new workers with re-deployed code. The old app version runs until it handles all pending TCP connections and afterward closes all existing client connections are gracefully. At the same time, the new app version accepts new client connections. Thus, the application is updated with no downtime or interruption in service.

Setting up a service before deployment

Before you deploy an application, you may want to set up the environment and configure the service.  Then, when you deploy the application to the service, it will run as you've configured it immediately.

To do this, first create a service in Process Manager as follows:



You don't have to create the service if you've already deployed an application to it: Deploy auto-creates the service (with default environment, and service name from the package.json), so you won't have to do slc create unless this is a brand new PM to which the app has never been deployed.

Then you can configure the environment, set the cluster size, and so on, before deploying: 

Then deploy your application to the service you previously created:

Next time you deploy, the service already exists, and if there is something you want to change, you simply use the following commands: 

  • No labels