The official balena CLI tool.
Go to file
2017-03-22 13:28:46 +03:00
bin Remove unused resin-write bin script 2015-08-19 11:30:48 -04:00
build allow specifying the version 2017-03-22 13:28:46 +03:00
doc build bare modules 2017-03-22 12:46:06 +03:00
extras/capitanodoc Regenerate docs 2015-07-07 18:01:25 -04:00
lib allow specifying the version 2017-03-22 13:28:46 +03:00
.editorconfig fix resin local push help message and lint errors 2017-03-21 12:06:05 +03:00
.gitignore Add resinrc.yml to gitignore 2015-09-08 09:07:48 +03:00
.hound.yml Change java_script to javascript in hound config 2015-10-19 14:21:10 -04:00
.npmignore Add npmignore 2015-12-04 08:51:28 -04:00
capitanodoc.json Docs: fix requirements for resin ssh and resin sync 2017-01-18 18:04:37 +02:00
CHANGELOG.md 5.5.0 2017-03-10 18:19:45 +00:00
coffeelint.json Add Coffeelint support 2014-10-31 09:48:53 -04:00
gulpfile.coffee build bare modules 2017-03-22 12:46:06 +03:00
LICENSE Change license to Apache 2.0 2016-01-03 23:58:51 -04:00
package.json build bare modules 2017-03-22 12:46:06 +03:00
README.md docs: rename 'Git Bash' to 'Git for Windows' 2017-01-18 19:33:49 +02:00
TROUBLESHOOTING.md Document the case where EACCES is thrown during login 2016-03-09 11:03:45 -04:00

Resin CLI

The official Resin CLI tool.

npm version dependencies Gitter

Requisites

  • NodeJS (at least v0.10)
  • Git
  • The following executables should be correctly installed in your shell environment:
    • ssh: Any recent version of the OpenSSH ssh client (required by resin sync and resin ssh)
    • rsync: >= 2.6.9 (required by resin sync)
Windows Support

resin sync and resin ssh have not been thoroughly tested on the standard Windows cmd.exe shell. We recommend using bash (or a similar) shell, like Bash for Windows 10 or Git for Windows.

If you still want to use cmd.exe you will have to use a package manager like MinGW or chocolatey. For MinGW the steps are:

  1. Install MinGW.
  2. Install the msys-rsync and msys-openssh packages.
  3. Add MinGW to the %PATH% if this hasn't been done by the installer already. The location where the binaries are places is usually C:\MinGW\msys\1.0\bin, but it can vary if you selected a different location in the installer.
  4. Copy your SSH keys to %homedrive%%homepath\.ssh.

Getting Started

Installing

This might require elevated privileges in some environments.

$ npm install --global --production resin-cli

List available commands

$ resin help

Run the quickstart wizard

$ resin quickstart

Plugins

The Resin CLI can be extended with plugins to automate laborious tasks and overall provide a better experience when working with Resin.io. Check the plugin development tutorial to learn how to build your own!

FAQ

Where is my configuration file?

The per-user configuration file lives in $HOME/.resinrc.yml or %UserProfile%\_resinrc.yml, in Unix based operating systems and Windows respectively.

The Resin CLI also attempts to read a resinrc.yml file in the current directory, which takes precedence over the per-user configuration file.

How do I point the Resin CLI to staging?

The easiest way is to set the RESINRC_RESIN_URL=resinstaging.io environment variable.

Alternatively, you can edit your configuration file and set resinUrl: resinstaging.io to persist this setting.

How do I make the Resin CLI persist data in another directory?

The Resin CLI persists your session token, as well as cached images in $HOME/.resin or %UserProfile%\_resin.

Pointing the Resin CLI to persist data in another location is necessary in certain environments, like a server, where there is no home directory, or a device running Resin OS, which erases all data after a restart.

You can accomplish this by setting RESINRC_DATA_DIRECTORY=/opt/resin or adding dataDirectory: /opt/resin to your configuration file, replacing /opt/resin with your desired directory.

Support

If you're having any problem, check our troubleshooting guide and if your problem is not addressed there, please raise an issue on GitHub and the Resin.io team will be happy to help.

You can also get in touch with us at our public Gitter chat channel.

License

The project is licensed under the Apache 2.0 license.