We implemented a internal Node application which has to be deployed to a number of devices(machines). We decided to use NPM for the automated software deployment. Because it is an internal application we created a private NPM registry on our servers and published our application on this registry. That works principally fine.
The problem is that our application depends on several other "public" packages like express, socket.io, moment etc. Each of these modules depends on other modules. At the end of the day, a graph of may be 30 packages needs to be handled. How to manage this situation in a efficient way with a private NPM repository? 1) Automated replication of the full npm registry from npmjs.org to our private repository: should work, we would have all needed packages (our own package as well as all dependencies) on our server and could distributed them to our client machines - however, this seems to be a little bit oversizes solution, doesn't it? 2) Telling the clients machines to install the "private" package from the private repository but all dependencies packages from the public npmjs.org registry - (how) could this work ?? 3) publish all dependencies (express, socket.io, moment etc.) manually on our private repository using "npm --registry [private registry] ....". This works some how but is a lot of work because of the many dependencies of the dependencies of the dependencies .... Any ideas how to improve it? Thanks! -- -- 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/d/optout.
