options for private npm registries?

[Laurie]

Hi, I'm looking into the options for setting up a private npm repository and the trade-offs in terms of operational and infrastructure costs. So far I've found:

 * irisnpm.com hosting; originally provided by Iris Couch, but seems to be unsupported / defunct?

 * GemFury npm hosting; inexpensive, but limited service plans, and no central registry mirroring :-/

 * set up a registry on a (hosted or internally managed) CouchDB instance, with mirroring of central registry

 * set up a registry without mirroring, use the new StrongLoop node dist's modified npm

Mirroring the central registry is sub-optimal (especially with a hosted Couch instance, given the resulting increase in costs); on the other hand, using a private registry without mirroring is rather limiting unless you use StrongLoop (or an otherwise patched npm or registry -- I think I saw a fork of the registry couch app that supported proxying to the central registry somewhere?).

Are there other options I'm missing? Are there plans to integrate StrongLoop's changes to npm in the (foreseeable ;-) future?

Thanks,

L.

[Luke Arduini]

AFAIK StrongLoop hasn't submitted a patch to npm. If they have some useful changes it would be great to see them upstream as well. 

--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
 
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[andy e]

In a similar boat, so interested to see what you find out/which route you take (previous thread I started at https://groups.google.com/d/topic/nodejs/sX4mbsRPwls/discussion).

There's things like node-reggie by Mike (https://github.com/mbrevoort/node-reggie) and I also just realized that you could just point to URIs for your dependencies (see the second answer at http://stackoverflow.com/questions/14609131/can-i-run-a-private-npm-repository-without-replicating-the-public-repository). That's not ideal obviously (I wrote a little script to help that will re-write the dependency in any package.json's of other modules I'm depending upon) but might end up working for us in our bizarro environment.

andy

--

[Nuno Job]

irisnpm is not dead. Has it failed for you?

Nuno

[Ben Noordhuis]

On Thu, May 2, 2013 at 12:11 AM, Luke Arduini <luke.a...@gmail.com> wrote:
> AFAIK StrongLoop hasn't submitted a patch to npm. If they have some useful
> changes it would be great to see them upstream as well.

The goal is to send everything upstream in the near future, where
'near' is on the order of a few weeks.

For anyone who is interested, our repository is here:
https://github.com/strongloop/npm

[Laurie]

Thanks Ben, that timeline is encouraging and in the meanwhile we can use the patched npm where adopting StrongLoop isn't an option. 

L,

[Laurie]

Yes, it wont recognize me as signed in. The persona signin process completes without (visible) error but I still get told to sign in first when trying to access my account. It's been that way as long as I've known about the service, in every browser I've tried. There's no support or contact info on the site, either, so I'm at a dead end :)

L.

[Mikeal Rogers]

I'd ping https://twitter.com/iriscouch , also Jason watches this list so he'll probably pop in once it's morning in Thailand :)

[Mikeal Rogers]

I'm curious, why do you want a private registry?

-Mikeal

[Laurie]

This is for work; we want to manage our internal modules with npm, but the code is proprietary so can't be published to the central registry. A private registry is the cleanest solution (vs. f.e. using url dependencies or something).

L.

[Matt]

On Thu, May 2, 2013 at 1:45 PM, Laurie <lau...@holoweb.net> wrote:

This is for work; we want to manage our internal modules with npm, but the code is proprietary so can't be published to the central registry. A private registry is the cleanest solution (vs. f.e. using url dependencies or something).

We just do this with private github repos and URL dependencies pointing direct to the github repo.

[Laurie]

Unfortunately, we don't use git. I could do something similar with `npm pack` and a shared file volume, but then we lose `npm publish` and, more significantly, fuzzy version matching. Propagating updates to a module with `npm version && npm publish` on one side, and `npm update` on the other, keeps things nice and simple :-)

L.

[Addison Higham]

I also have tried using irisnpm and haven't been able to get the persona login to work. 

I messaged iriscouch on twitter ages ago and never got a response. I would love to try it out!

Addison

L.

--