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 On Wed, May 1, 2013 at 3:58 PM, Laurie <[email protected]> wrote: > 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. > > -- > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected] > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
