Trouble with default local registry in README #42

Closed
robertjustjones opened this Issue Mar 3, 2014 · 5 comments

Comments

Projects
None yet
2 participants
Contributor

robertjustjones commented Mar 3, 2014

I followed the README for "paths" option in config.json
"paths": [ "http://localhost:5984/registry/_design/ghost/_rewrite/", ...]
and couldn't read from local. I also tried the following which matches my npm config
"paths": [ "http://localhost:5984/registry/_design/app/_rewrite/", ...]
but that didn't work either. However, the following works beautifully.
"paths": [ "http://localhost:5984/registry/", ...]
Has something changed in the code to make this shortened version work and/or is there something else I've configured that dictates this form? I'm not using the registry vhost'ing that allows https://registry.npmjs.org to work. Either way, we should clarify the README.

Thanks! Love what you've done with kappa.

Owner

totherik commented Mar 3, 2014

Hey @robertjustjones you're correct, the example is wrong. Fixing now, but should be:
http://localhost:5984/registry/_design/app/_rewrite/ (not ghost). As to why it's not working for you, I'll have to debug further. I'll let you know what I find.

Owner

totherik commented Mar 3, 2014

@robertjustjones what steps did you go through to set up the couchdb instance you're referencing above? Did you follow all the instructions found here? https://github.com/npm/npmjs.org

Contributor

robertjustjones commented Mar 3, 2014

It's been a while, and in with an earlier version, but yes I followed roughly those instructions. What has me curious is that I do use the full design doc path http://localhost:5984/registry/_design/app/_rewrite/ for direct access with npm. Maybe it's time to rebuild my registry.

Contributor

robertjustjones commented Mar 4, 2014

@totherik fyi, I setup up a completely new npmjs.org w couchdb 1.5 using all the instructions above. It works with both http://localhost:5984/registry/ and http://localhost:5984/registry/_design/app/_rewrite/. I like the former... hope that won't get broken.

Owner

totherik commented Mar 4, 2014

Wow, interesting. Well, unfortunately you have to use the latter otherwise not all operations will work correctly. See here: https://twitter.com/izs/status/440581099496808448

@totherik totherik closed this Mar 4, 2014

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