The official balena CLI tool.
Go to file
2015-03-02 12:34:15 -04:00
bin Fix NODE_PATH issue 2015-02-27 14:20:56 -04:00
build Document --quiet option for plugin install 2015-03-02 10:41:38 -04:00
completion Update sh completion with new commands 2015-02-09 10:00:16 -04:00
lib Document --quiet option for plugin install 2015-03-02 10:41:38 -04:00
man Increment man page month 2015-03-02 10:40:43 -04:00
release/installers Fix Windows installer PATH 2015-02-27 15:05:15 -04:00
tests Move tests to tests/ and flatten errors/ module directory 2015-02-10 11:38:19 -04:00
.editorconfig Add editorconfig 2014-10-31 09:49:57 -04:00
.gitignore Remove useless npm-shrinkwrap.json 2015-03-02 12:27:30 -04:00
coffeelint.json Add Coffeelint support 2014-10-31 09:48:53 -04:00
gulpfile.coffee Reference JavaScript version of install-node script 2015-02-26 11:50:21 -04:00
Makefile Make sure distrib/ exists when creating os x installer 2015-02-27 13:31:17 -04:00
package.json Implement plugin update command 2015-03-02 10:41:08 -04:00
README.md Add dependencies and Travis CI badges 2015-03-02 12:34:15 -04:00

Resin CLI

dependencies Build Status

Take a look at the spec for features, roadmap and progress https://docs.google.com/a/resin.io/document/d/1mPBWy9wwLiNd25VcIvp3HEWJNjoXkALfMLMblXaGoh8/edit?usp=sharing.

Installing

$ git clone git@github.com:resin-io/resin-cli.git
$ cd resin-cli
$ npm install

If you want to have resin on your PATH:

$ npm install -g

If you want to run it locally:

$ ./bin/resin

Or:

$ node build/app.js

Tests

You can run the Mocha test suite, you can do:

$ gulp test

Development mode

The following command will watch for any changes and will run a linter and the whole test suite:

$ gulp watch

If you set DEBUG environment variable, errors will print with a stack trace:

$ DEBUG=true resin ...

Release

The following command will compile the application into a single executable for the current platform (supports Mac OS X, GNU/Linux and Windows > XP):

$ gulp release

The binary will be located at build/Release.

Documentation

You can renegerate the documentation with:

$ npm run-script doc

Manual pages

UNIX manual pages reside in man/

You can regenerate UNIX roff manual pages from markdown with:

$ gulp man

If you add a new man page, remember to add the generated filename to the man array in package.json.

Caveats