To install the latest version of npm On-Site, you need a server fulfilling these basic specs:
If using Amazon Web Services, see note on AWS below.
We have tested extensively on the operating systems listed above. It may be possible to run npm On-Site on other systems, but, at this time, no other systems are officially supported.
We do our best to support as many systems as possible. If you have special requirements or feedback for other platforms, please reach out to us at support@npmjs.com. We'd love to work with you.
You can also check for system issues on the npmo-installer GitHub repo.
The amount of disk space needed is directly proportional to the number and size of packages your registry will need to host.
For example, the full public registry hosts at least 200,000 packages with an average of 6 versions each, and this requires at least half a terabyte of storage. Smaller registries, however, can get away with just a few gigabytes.
Therefore, a server with 50 - 100 GB is a good choice for most registries.
Please reserve at least 6 GB for OS resources and npm On-Site appliance containers.
Once installed, you can configure where registry data is stored on your server via the "Storage" paths on the "Settings" page of the admin web console (port 8800). For details on configuring your On-Site instance, please see this page.
We recommend using an m3.large instance type.
If extra storage is needed, you may want to attach an EBS volume to your EC2 instance and configure the "Storage" paths on your On-Site appliance to use directories under the mount point.
To open ports on your AWS EC2 instance, you can define a Security Group with the following Inbound settings:
Last modified February 11, 2016 Found a typo? Send a pull request!