The official balena CLI tool.
Go to file
2015-01-09 14:13:13 -03:00
bin Remove JS compilation step for running bin/resin 2014-12-09 15:40:38 -04:00
completion Implement devices supported command 2014-12-24 12:50:30 -04:00
lib Get rid of cache module 2015-01-09 13:41:32 -03:00
man Partially get rid of nested sdk 2015-01-08 09:39:38 -03:00
scripts Implement of unix installation script 2014-12-31 11:22:52 -04:00
tests/fixtures Get rid of utils/mock 2015-01-08 09:43:50 -03:00
.editorconfig Add editorconfig 2014-10-31 09:49:57 -04:00
.gitignore Include gulp compile task 2014-12-30 09:44:03 -04:00
coffeelint.json Add Coffeelint support 2014-10-31 09:48:53 -04:00
gulpfile.coffee Implement gulp release task 2014-12-30 13:12:18 -04:00
package.json Remove unused NPM dependencies 2015-01-09 14:13:13 -03:00
README.md Explain how to produce a binary in README.md 2014-12-30 13:20:07 -04:00

Resin CLI

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@bitbucket.org:rulemotion/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:

$ coffee lib/app.coffee

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

  • Some interactive widgets don't work on Cygwin. If you're running Windows, it's preferrable that you use cmd.exe, as Cygwin is not official supported by Node.js.
  • Most commands require an <id> argument, however Commander refuses to show that in the help page. This will be fixed soon.