I personally feel it's a pretty nifty way to do things (modulo the use of -g).
On Jun 4, 3:57 pm, José F. Romaniello <jfromanie...@gmail.com> wrote: > Hi list, I was thinking today if npm is the right tool to "deploy" or > install my application in servers or vms i own. > Doing: > > npm install git://myprivategit-repo -g > > From the vm and then some scripts to "daemonize" it. I am currently > deploying to windows, and converting it to a windows service(no iisnode). > But i think some of the thoughts i have so far are also valide for nix: > > -is this a bad practice? > > Cons: > -the other thing doesnt feel right is that global packages ends in a folder > inside the user home. And this is not usually the standard place to put an > application. > -i have to log to the server to update! Maybe i can put another thing > listening to updates/ and then do npm update xx > > Pros: > -super easy to set up > > The other scernario o have explored is to have the folder as a git end > point (and a post receive hook) and pushing to that remote whenever i want > to update. This is hard to set up this in windows at least.. But seems > better in the long run, as the vms and nodes grow. > > Also I saw Isaacs fleet, looks very cool but havent tried yet. > > Thoughts? > > Thanks in advance! -- 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
