Juan Cruz Viotti dc257b5cab Check token validity against the API when login
Consider the following case:

The SDK is configured to point to staging, but the user passes a token
from production, or viceversa. Since the token is valid in a sense that
is valid JWT and contains real data, the CLI will report as a success.

The user will then get Unauthorized errors when using the API.
2015-09-05 20:17:34 +03:00
2015-08-19 11:30:48 -04:00
2015-09-01 13:01:47 -04:00
2015-07-07 18:01:25 -04:00
2014-10-31 09:49:57 -04:00
2015-04-06 17:05:13 -04:00
2015-04-06 10:08:49 -04:00
2015-08-06 12:12:44 -04:00
2015-08-28 08:22:26 -04:00
2015-08-27 15:30:38 +03:00
2014-10-31 09:48:53 -04:00
2015-08-04 10:00:09 -04:00
2015-03-05 15:43:39 -04:00

Resin CLI

npm version dependencies Build Status Build status

The official Resin CLI tool.

Installing

$ npm install -g resin-cli

Running locally

$ ./bin/resin

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 ...

Documentation

You can renegerate the documentation with:

$ npm run-script doc

Caveats

Description
The official balena CLI tool.
Readme Pixar 73 MiB
Languages
TypeScript 97.9%
JavaScript 1.5%
Shell 0.4%
EJS 0.1%