search

mbrevoort / node-reggie

An experimental light weight alternative to a full blown npm registry
416 stars 50 forks source link

Why doesn't Kappa + Reggie work? #49

Closed parris closed 10 years ago

parris commented 10 years ago

I'm trying to put both the npm registry (with nginx proxy cache) and reggie behind kappa. Kappa should try to get a package from the npm registry and proxy cache then fail and fall back to reggie. That doesn't currently happen.

If someone gets to this before me then awesome. Otherwise, I'll check it out myself.

By the way this is an awesome package! We are using it here at Eventbrite. Also putting it in my presentation for HTML5 dev conf in SF. Let me know if you guys need any help.

Thanks!

leftieFriele commented 10 years ago

I used kappa in front of reggie, but we had reggie as the first item in the list. Then kappa fell back if the module didn't exist in our local repo which only had the modules which should remain private.

however we since moved away from reggie after advice from the module owners that reggie wasn't being updated anymore.

parris commented 10 years ago

@leftieFriele that makes sense. Also, that's a bummer, why did they stop updating? Not everyone wants to be a couchdb sysadmin.

Also what are you using now instead (if anything)?

parris commented 10 years ago

I just read, the pull request. Sinopia looks cool. I'll ride out node-reggie for a little while. Hopefully, breaking changes don't come to npm in the next year. Although I've heard private npm stuff is supposed to be easier and built in, in the future...

leftieFriele commented 10 years ago

We've moved to Sinopia without any problems. Using it you don't have to use Kappa either as it has support for querying multiple repos and cache artifacts. On May 17, 2014 9:31 PM, "Parris Khachi" notifications@github.com wrote:

I just read, the pull request. Sinopia looks cool. I'll ride out node-reggie for a little while. Hopefully, breaking changes don't come to npm in the next year. Although I've heard private npm stuff is supposed to be easier and built in, in the future...

— Reply to this email directly or view it on GitHubhttps://github.com/mbrevoort/node-reggie/issues/49#issuecomment-43422028 .