@nuskin/rosiedeployer

Module that does a rosie deploy

Stats

StarsIssuesVersionUpdatedCreatedSize
@nuskin/rosiedeployer
0.0.143 years ago3 years agoMinified + gzip package size for @nuskin/rosiedeployer in KB

Readme

Rosie Deployer

The rosiedeployer can deploy npm package to rosie - similar to the maven plugin.

Installation

To use it in an npm module, simply install it as a development dependency like this:

npm install rosiedeployer -D

Configuration

Thereafter, edit the package.json and add the deployer to the 'scripts' section of the package.json of your project like this:

{ "name": "my-project", "version": "1.0.0", "baseURL": "/", "main": "src/main.js", "scripts": { "rosie-deploy": "rosie-deploy" },...

By default, the rosiedeployer will use the "name" and "version" properties of the package.json to deploy the artifact to development.

The deployer also expects a file on your system at /opt/jenkins_home/.jenkins_info to contain a username and password for Rosie. (username first, password 2nd, properties style. i.e. username=someuser, password=somepass)

This can be overridden by using a "rosieDeploy" section in your package.json, like this example:

... "rosieDeploy": { "username": "myuser", "password": "mypass", "deployable": "mydeployable", "version": "1.0.0-SNAPSHOT" }, ...

Execution

Then you can execute the rosie deploy like this:

npm run rosie-deploy

By default the rosieDeployer gets installed into the node_modules/.bin directory. That is why it can be run as an npm script.

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.