Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

Post: An Aussie npm mirror to kill the latency #11

Open
rvagg opened this issue Jul 27, 2013 · 7 comments
Open

Post: An Aussie npm mirror to kill the latency #11

rvagg opened this issue Jul 27, 2013 · 7 comments

Comments

@rvagg
Copy link
Member

rvagg commented Jul 27, 2013

Update 2014-02-06: See npm.nodejs.org.au for updated instructions on how to set up your npm client to pull from the Australian mirror.


Installing from npm is always a pain from this side of the planet, particularly when you have a lot of dependencies to install and particularly when you've experienced it from a computer located in North America.

For a little while now I've been maintaining a mirror of the npm registry running out of the AWS datacentre in Sydney and it's an absolute pleasure to be able to npm install and have it complete in a couple of seconds. I'm now confident enough to share it with anyone else who would like to be able to do quick installs.

All you need to do is put this line in your ~/.npmrc file:

registry = http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite

You won't be able to publish to it, so you have switch back to the standard registry to do that. You either have to remove or comment out that line, or be a little more clever.

Thankfully, @deoxxa has already thought of this and has a great script that I can recommend: npmrc.

Simply make a ~/.npmrcs/ directory and put alternative .npmrc files in it with names indicating their use. For example, I have one named write that uses the global registry and one called read that uses npm.nodejs.org.au. When I want to switch between them I just type npmrc read or npmrc write and it switches a symlink from ~/.npmrc to the appropriate file in ~/.npmrcs/.

(If you're running your own mirror, please continue to replicate from the global registry, Joyent can afford the bandwidth more than me.)

Enjoy!

@simonexmachina
Copy link

I can't access this repo - I get 401. Tried to login but no dice...

@eugeneware
Copy link
Member

Use npmrc (https://npmjs.org/package/npmrc) with the following .npmrc
config:

email = [email protected]
registry = http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite

remove all the [_token] and _auth stuff from it. It's a read only DB.

On Wed, Sep 25, 2013 at 11:51 AM, simonwade [email protected]:

I can't access this repo - I get 401. Tried to login but no dice...


Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-25057024
.

Eugene Ware
Chief Executive Officer

Phone: +61 3 9955 7041
Email: [email protected]
Twitter: @eugeneware http://twitter.com/EugeneWare

Noble Samurai Pty Ltd
Level 1, 234 Whitehorse Rd
Nunawading, Victoria, 3131, Australia

noblesamurai.com http://www.noblesamurai.com/ | eugeneware.com |
facebook.com/Eugene.S.Ware http://www.facebook.com/Eugene.S.Ware

@simonexmachina
Copy link

Great, thanks.

@jpillora
Copy link

jpillora commented Jun 4, 2014

@rvagg Should this mirror be up? http://npm.nodejs.org.au

502 Bad Gateway
nginx/1.6.0

@rvagg
Copy link
Member Author

rvagg commented Jun 4, 2014

@jpillora set your registry to http://registry.npmjs.org.au instead. I'm still getting that server sorted out in my spare time but the registry should be working.

@rvagg
Copy link
Member Author

rvagg commented Jun 4, 2014

@jpillora was a bit out of sync but pretty much caught up now if you want to use registry.npmjs.org.au.

I have an SSL cert for it too that I'll get set up when I have time.

@jpillora
Copy link

jpillora commented Jun 4, 2014

Awesome thanks Rod!

On Thursday, June 5, 2014, Rod Vagg [email protected] wrote:

@jpillora https://github.com/jpillora was a bit out of sync but pretty
much caught up now if you want to use registry.npmjs.org.au.

I have an SSL cert for it too that I'll get set up when I have time.


Reply to this email directly or view it on GitHub
#11 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants