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

Getting Started

In this getting started guide you will get setup with your Hosted Private npm registry from Nodejitsu as well as learn about some of the best practices for working with package.json files.

But first, take a look at this 4 minute introduction to our Private npm solution.

1. Configure the npm CLI

Just like the public registry, the npm CLI program is what you'll use to install, publish and otherwise interact with npm modules. Nodejitsu Enterprise private npm has two changes in the configuration to your npm CLI client:

$ npm config set always-auth true
$ npm config set strict-ssl true
$ npm config set ca ""

Why do you need to do these things?

  • Every request requires authentication: This means that users you have not authorized cannot download packages from your private npm. Since this is not the default behavior of the public npm you need to set:
$ npm config set always-auth true
  • Be strict about SSL: We improved our SSL experience, now our Private npm registry supports multi-level wildcard certificate issued by DigiCert and serves https://*, so you'll need to set the following to your npm config:
$ npm config set strict-ssl true
$ npm config set ca ""

2. Login & start making requests against your private npm

Requests can be made against your private npm in two ways:

  • Set the registry for all requests: This means that every request will hit your private registry
    $ npm config set registry
  • Use the --reg flag when necessary: The --reg flag (short for --registry) will allow you to make any request against your private registry:
    $ npm login
    $ npm info your-private-module --reg

We recommend thatyou set the registry for all requeststo avoid any accidental publishes of private modules to the public registry. Since all new publishes go by default to your private npm registry when you needto publish a new public npm package** you can explicitly set the --reg flag:

  $ cd /my/new/public/package
  $ npm init
  $ npm publish --reg

More information available at the Command Line Interface Documentation

3. Login to the Web Interface

More information available at the Web Interface Documentation

PROTIP: Publish modules using publishConfig

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.

For example:

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

The benefits of using publishConfig is that it avoids accidental publishes to the public registry due to user error. Take for example a developer on your team who has not properly configured their machine by running npm config set registry or using the --reg flag. That command would send your code public. By using the publishConfig property you avoid that because it is part of your application.

Getting Started

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

See the guide