I had to do this a couple of months ago, and I found that using a private repo for code and building tagged releases using "npm pack" worked well for me.
The company I was working for stored all of its deployment packages in Amazon S3. We considered using the git+ssh approach, but our general approach to managing releases (with other technologies) was to build archival packages, so installing from a tarball worked well for us. At the time I put together a simple module to support the workflow we were using: https://github.com/ccare/node-release-utils Cheers, Charles On 11 October 2012 07:52, Julian Gruber <misterio...@googlemail.com> wrote: > use /lib or put modules in a git repo (you can host them yourself too) and > reference them with git:// or git+http://. > > -- > 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
