Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

README is wrong (app -> scratch) #72

Closed
mlinenweber opened this Issue · 9 comments

8 participants

@mlinenweber

The README says to use a private registry http://localhost:5984/registry/_design/app/_rewrite but it looks like "app" should now be "scratch". Revision 7c99208 of registry/app.js looks to have changed this.

@isaacs
Owner

You can also just do what the message says when you run it.

I've been meaning to have it actually run the curl for the particularly slow views (mostly, search) and then do the HTTP COPY right there. Just haven't gotten around to it.

@diversario

Also, README probably should mention use of push.sh, along with setting the npm_package_config_couch to the couchdb address. It definitely makes things easier.

@wyrdvans

@diversario What is npm_package_config_couch? environment variable? config file? Can you provide an example of the contents?

@diversario

@wyrdvans Umm, yes, I think it was an env variable. I'm sorry, I got it working and then it turned out that another person is working on it, so I stopped. Set it to the HTTP address of your couchdb instance.

@isaacs
Owner

@wyrdvans An environment variable, which you can also set via:

npm config set couch=http://localhost:5984/registry

Or, to prevent it from being seen by any other package's start/install scripts:

npm config set _npmjs.org:couch=http://localhost:5984/registry
@motin

Actually, those suggestions still lead to "Please set a valid 'npmjs.org:couch' npm config." when running push.sh

Only this worked:

export npm_package_config_couch=http://localhost:5984/registry
./push.sh
@icodeforlove

i got bit by the examples using app instead of scratch too

@gmaggess

I've followed the steps on the README.md file, and I've got no error. However, I can't find a _design/app document under registry. I see _design/scratch and _design/ui. Is that right?

I tried to follow Isaac's instructions on a different thread [#103 (comment)] but got no luck. This is the error I got doing 'npm start':

~/Developer/myprojects/github/npmjs.org on master*
$ export npm_package_config_couch=http://admin:Welcome1@slc01pvp:5984/registry
~/Developer/myprojects/github/npmjs.org on master*
$ npm config set couch=http://admin:Welcome1@slc01pvp:5984/registry
~/Developer/myprojects/github/npmjs.org on master*
$ npm start

npmjs.org@1.0.1 start /Users/gmaggess/Developer/myprojects/github/npmjs.org
./push.sh

Please set a valid 'npmjs.org:couch' npm config.

You can put PASSWORD in the setting somewhere to
have it prompt you for a password each time, so
it doesn't get dropped in your config file.

If you have PASSWORD in there, it'll also be read
from the PASSWORD environment variable, so you
can set it in the env and not have to enter it
each time.
npm ERR! npmjs.org@1.0.1 start: ./push.sh
npm ERR! sh "-c" "./push.sh" failed with 1
npm ERR!
npm ERR! Failed at the npmjs.org@1.0.1 start script.
npm ERR! This is most likely a problem with the npmjs.org package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ./push.sh
npm ERR! You can get their info via:
npm ERR! npm owner ls npmjs.org
npm ERR! There is likely additional logging output above.

npm ERR! System Darwin 12.3.0
npm ERR! command "node" "/usr/local/bin/npm" "start"
npm ERR! cwd /Users/gmaggess/Developer/myprojects/github/npmjs.org
npm ERR! node -v v0.8.18
npm ERR! npm -v 1.1.71
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/gmaggess/Developer/myprojects/github/npmjs.org/npm-debug.log
npm ERR! not ok code 0

I've also tried to setup the environment variable suggested here [motin@4cc3422], but got the same error.

Any help is appreciated.

@terinjokes
Collaborator

The README was vastly improved a few weeks back, and should now accurately reflect how to create a private repository.

If there are issues following the new documentation, please open a new issue.

@terinjokes terinjokes closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.