Hi Andy, I posted a detailed answer, but did not show up here. Hope this one does.
Here is a quickstart : http://docs.strongloop.com/display/DOC/Setting+up+a+private+package+registry We are also building a self-contained lightweight repo server not depending on external services, i.e. using embedded db or filesystem instead of CouchDB + Redis. We use artifactory today and are trying to bridge Reggie to Artifactory for a comprehensive private solution. Let me know if you want to collaborate -Shubhra Kar Product Manager, StrongLoop *Using the current version of reggie as a private/on-premise NPM registry* *Setup:* # run on the server npm install -g reggie reggie-server -d {store-directory} *Publish a package:* # run on developer's machine npm install -g reggie reggie -u http://reggie:8080/ publish # run inside your package/module folder *Add the package as a dependency* # package.json: dependencies: { "foo": "http://reggie:8080/package/foo/0.1.0" } # Command-line version npm install --save http://localhost:8080/package/foo/0.1.0 See reggie documentation<https://github.com/mbrevoort/node-reggie#resolving-packages-from-reggie> for the description of all possible version strings (e.g. latest or 0.1.x). On Monday, February 18, 2013 10:23:05 AM UTC-8, andy wrote: > > Apologies in advance because I've only glanced at this problem, but we > work in a unique environment where we have no Internet connectivity. > So, with our Java apps, we run an instance of Artifactory on our LAN and > load it by running an instance that is connected, which we then export and > bring into the 'offline' instance. That gives us a sort of mirror of Java > dependencies for maven and what not when we're developing. > > Is there anything like Artifactory for npm? Do I need to roll my own > somehow (i.e. would a simple WebDAV server work or is it more complex)? > > I've glanced at Mike's node-reggie idea so maybe that is a place to start ( > https://github.com/mbrevoort/node-reggie). > > We don't need anything fancy - just a way to add npm modules to a project > without having to check them in or pass around a giant .zip copy with all > possible repos...etc. (Right now I just have a "node_modules_for_work" > folder where I load up a ton of modules, then I zip that up and bring it > in.) > > I'm happy to go off and do some reading/digging, so links to similar > ideas/attempts are appreciated. > > Thanks, > > Andy > -- -- 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.
