Nodejitsu has joined GoDaddy
We are excited to join GoDaddy to help spearhead their largest Node.js product: Website Builder. As a part of this Nodejitsu will help existing customers transition onto new solutions for their hosting needs until early August 2015. Please migrate your applications from the Nodejitsu platform before the end of the transition period. Please read our blog post to learn more about customer transition plans and our continued support for Open Source within the node community.
Fork on Github

Configuring jitsu

To show your current jitsu configuration do jitsu conf. Results will contain information about our API location, your username and authentication token. Username and token have been removed from the example below but should contain details specific to your account.

data:    {
data:        directories: {},
data:        userconfig: '/home/user/.jitsuconf',
data:        remoteHost: '',
data:        username: '[username]',
data:        apiToken: '[token]'
data:        apiTokenName: '[tokenname]',
data:        rejectUnauthorized: false
data:    }

Changing any of the keys is possible through jitsu config set [key] [value]. For example, to change the username to any alternative username execute jitsu config set username otherusername. Note that the command for changing settings is jitsu config not jitsu conf!

Command specific flags

Jitsu also provides a myriad of different flags that can be appended to each command, here is a short overview.


Appending --release or -r will allow you to specify a release version number or semantic increment, e.g: build, patch, minor, major. For example jitsu deploy --release minor will increment the minor version number (build version increment is default).


Changing color output is available through --colors. By default coloring of output is on, this can be disabled by appending --no-colors.


If you are confident on jitsu actions you can prevent additional prompts to confirm actions by appending --confirm or -c.

Alternative configuration

Any alternative jitsu configuration can be loaded from file, without switching accounts.

Local and parent directories: Append --localconf

Specified file location: Append --jitsuconf or -j followed by file location.


Useful for support questions and the like, aquire your current jitsu version by appending --version or -v.

Skip analyzing

Skipping dynamic dependency detection can be done by appending --noanalyze.

Raw output

If you need all jitsu output as raw JSON, e.g. for piping, append --raw.

Getting Started

Learn how to set up Nodejitsu's tool for app deployment and be ready for action.

See the guide