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

Building applications:

  1. Install dependencies
  2. Bundle dependencies
  3. Create deploy package, either:

Use slc build --pack to create a portable archive, a tar (.tgz) file that you can then deploy to StrongLoop Process Manager.  This is the default for slc build if there is no .git directory in the current working directory (that is, if the application is not cloned from a Git repository).

Slc puts the archive file in the parent directory of the application, to avoid the archive file itself getting packed by future builds, and to make it easier to clean the working repository.  The archive file name starts with the application name and version number specified in package.json, for example, for the initial version of an application called "myapp," the file is myapp-0.0.0.tgz.

When you subsequently use the slc deploy command, it will look for a .tgz file to deploy based on the application name and version number specified in package.json in the current directory.

If the bundle command created a .npmignore file, check the pack file contents carefully to ensure build products are packed, but project ephemera are not.  See Using a .npmignore file for more information.

  • No labels