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

Hosted private npm FAQ

Will my private registry stay up If the public registry goes down?

Yes, it will remain online and you will be able to use npm without problems.

Can anyone else access my registry?

Only the team members defined in the Web Interface can access your registry.

How can I make sure I don't accidentally publih to the public registry?

We recommend that you set the default to private npm registry. This removes even the slightest chance that your private code could get published publicly accidentally.

npm config set https://{your-subdomain}

Alternatively, if you're feeling bold: you can use the publishConfig property in your package.json:

For example:

    "publishConfig": { "registry": "" }

The publishConfig in your package.json does the following (from the npm documentation):

This is a set of config values that will be used at publish-time. It's especially handy if you want to set the tag or registry, so that you can ensure that a given package is not tagged with "latest" or published to the global public registry by default.

Any config values can be overridden, but of course only "tag" and "registry" probably matter for the purposes of publishing.

What happens if I need to change my password on the public npm registry?

You will need to resync your new password with your private npm registry. Youc an do this by:

$ npm config set registry
$ npm login

Getting Started

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

See the guide