Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
# use the npm mirror:
npm set registry http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com
# you can reset this later with npm set registry npm set registry https://registry.npmjs.org/
# then use it normally:
npm install express
@streunerlein

This comment has been minimized.

Show comment Hide comment
@streunerlein

streunerlein Aug 12, 2012

UPDAte.

Owner

streunerlein commented Aug 12, 2012

UPDAte.

@streunerlein

This comment has been minimized.

Show comment Hide comment
@streunerlein

streunerlein Aug 12, 2012

Please note: This mirror is not meant to do npm publish, it's just a readonly mirror. And please don't mess up things in the db, i didn't close write access atm.

Another please: Contact me if you experience slowliness, I will then set up more mirrors and maybe a load balancer so we have only one domain for it.

Owner

streunerlein commented Aug 12, 2012

Please note: This mirror is not meant to do npm publish, it's just a readonly mirror. And please don't mess up things in the db, i didn't close write access atm.

Another please: Contact me if you experience slowliness, I will then set up more mirrors and maybe a load balancer so we have only one domain for it.

@streunerlein

This comment has been minimized.

Show comment Hide comment
@streunerlein

streunerlein Aug 12, 2012

I'm seeing many 404 because people use the old url (with /registry). Make sure you use that one in the gist above, there has been an update.

Owner

streunerlein commented Aug 12, 2012

I'm seeing many 404 because people use the old url (with /registry). Make sure you use that one in the gist above, there has been an update.

@mren

This comment has been minimized.

Show comment Hide comment
@mren

mren Aug 12, 2012

i'm getting a redirect to registry.npmjs.org


% npm install sendgrid
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/sendgrid/0.2.4
npm http 404 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/sendgrid/0.2.4
npm http GET http://registry.npmjs.org/-/sendgrid-0.2.4.tgz
npm http 404 http://registry.npmjs.org/-/sendgrid-0.2.4.tgz
npm ERR! fetch failed http://registry.npmjs.org/-/sendgrid-0.2.4.tgz

do you know why this could happen?

mren commented Aug 12, 2012

i'm getting a redirect to registry.npmjs.org


% npm install sendgrid
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/sendgrid/0.2.4
npm http 404 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/sendgrid/0.2.4
npm http GET http://registry.npmjs.org/-/sendgrid-0.2.4.tgz
npm http 404 http://registry.npmjs.org/-/sendgrid-0.2.4.tgz
npm ERR! fetch failed http://registry.npmjs.org/-/sendgrid-0.2.4.tgz

do you know why this could happen?

@mren

This comment has been minimized.

Show comment Hide comment
@mren

mren Aug 12, 2012

ah it is not found in your repository^^

mren commented Aug 12, 2012

ah it is not found in your repository^^

@derickbailey

This comment has been minimized.

Show comment Hide comment
@derickbailey

derickbailey Aug 12, 2012

failing to parse json from OSX 10.8 (Mountain Lion) w/ NPM 1.1.45

$ npm install
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt-rigger
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt
npm http 200 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt
npm ERR! registry error parsing json
npm http 200 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt-rigger
npm ERR! registry error parsing json
npm http GET http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm http 404 http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm ERR! fetch failed http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm ERR! Error: 404 Not Found

failing to parse json from OSX 10.8 (Mountain Lion) w/ NPM 1.1.45

$ npm install
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt-rigger
npm http GET http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt
npm http 200 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt
npm ERR! registry error parsing json
npm http 200 http://ec2-46-137-149-160.eu-west-1.compute.amazonaws.com/grunt-rigger
npm ERR! registry error parsing json
npm http GET http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm http 404 http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm ERR! fetch failed http://registry.npmjs.org/-/grunt-0.3.12.tgz
npm ERR! Error: 404 Not Found
@tbigueres

This comment has been minimized.

Show comment Hide comment
@tbigueres

tbigueres Aug 12, 2012

@tbigueres

This comment has been minimized.

Show comment Hide comment
@tbigueres

tbigueres Aug 12, 2012

You can use this mirror (which fetches the original content from registry.npmjs.org). All modules up to date:

npm set registry http://85.10.209.91/

To reset:
npm set registry http://registry.npmjs.org/

You can use this mirror (which fetches the original content from registry.npmjs.org). All modules up to date:

npm set registry http://85.10.209.91/

To reset:
npm set registry http://registry.npmjs.org/

@johankool

This comment has been minimized.

Show comment Hide comment
@johankool

johankool Aug 12, 2012

Thanks @tbigueres!

Thanks @tbigueres!

@streunerlein

This comment has been minimized.

Show comment Hide comment
@streunerlein

streunerlein Aug 12, 2012

Mirror closed, npm working again.

Owner

streunerlein commented Aug 12, 2012

Mirror closed, npm working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment