Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

strong-deploy

Package Overview
Dependencies
Maintainers
5
Versions
24
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

strong-deploy

Deploy a node application to a StrongLoop process manager

  • 2.0.0
  • canary
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
122
decreased by-8.27%
Maintainers
5
Weekly downloads
 
Created
Source

strong-deploy

Deploy a node application package to the StrongLoop process manager, strong-pm.

Both git branches and npm packages can be deployed. They will typically be prepared using strong-build.

For more details, see http://strong-pm.io.

Installation

sl-deploy is made available through the strongloop tool as slc deploy, and works well with the StrongLoop Process Manager, strong-pm.

sl-deploy can be installed standalone with:

npm install -g strong-deploy

Usage

usage: sl-deploy [options] [URL [PACK|BRANCH]]

Deploy a node application to a StrongLoop process manager

Options:
  -h,--help          Print this message and exit.
  -v,--version       Print version and exit.
  -c,--config CFG    Deploy a specified configuration (default is "default").

Arguments:
  URL: The URL of the StrongLoop process manager.

    Defaults to `http://localhost:8701`. If a URL is provided, both the host
    and port is optional, they default to `localhost` and 8701, respectively.
    If the server requires authentication, the credentials must be part of the
    URL, see examples.

    URL may also use the `http+ssh://` protocol which will connect using ssh
    and then tunnel the http requests over that connection. The ssh username
    will default to your current user and authentication defaults to using your
    current ssh-agent. The username can be overridden by setting an `SSH_USER`
    environment variable. The authentication can be overridden to use an
    existing private key instead of an agent by setting the `SSH_KEY`
    environment variable to the path of the private key to be used.

  PACK: Deploy an NPM package/tarball.

  BRANCH: Deploy a git branch.

Default behaviour is to deploy to `http://localhost:8701`. An npm package from
the parent directory is deployed, if one is found for the current application
version, otherwise the git branch `deploy` is deployed.

Note that if PACK or BRANCH is specified, URL *must* be specified as well.

Examples:

Deploy the default npm package or git branch to localhost:

    sl-deploy

Deploy the default npm package or git branch to a remote host:

    sl-deploy http://prod1.example.com

Deploy to a remote host, on a non-standard port, using authentication:

    sl-deploy http://user:pass@prod1.example.com:8765

Deploy 'production' branch to localhost:

    sl-deploy http://localhost production

License

strong-deploy uses a dual license model.

You may use this library under the terms of the Artistic 2.0 license, or under the terms of the StrongLoop Subscription Agreement.

Keywords

FAQs

Package last updated on 30 Apr 2015

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc