On May 25, 2014, at 8:32 AM, Jake <[email protected]> wrote: > I'd like to know what people have done for node.js application deployments. > > Coming from a compiled-language background, I'm used to compiling things, > packing them up into some artifact, and deploying that to a server. This > seems unnecessary in node though. >
I think it is not needed. Maybe if you’re using binary modules for node (there’s not a lot of common ones, but they exist!). Most of those concerns, though, go away if your development and production environment are the same OS and revision. I don’t check my dependencies in to my git repos, though, so if you want to lock those down, this can be one way to accomplish that. > A few questions on this: > • Have you seen any benefit to packing up (perhaps just a zip file) all > the files from a node application and putting that in an artifact repository? Not really — unless it simplifies transporting things to servers. I treat it as a transfer tool, not an artifact. It can get you verifiability with a hash; that said, git gets you that too. > • Is there any reason not to just tag the source repo and copy (rsync, > scp, etc) the files to the servers from there? Not at all. Also consider git — it’s quite good for this! > • Is there any benefit to publishing the application to an internal npm > repository and deploying from there? I wouldn’t say so. Often with an application, you want to control where it’s unpacked and run from, and don’t particularly want it in some global path. Aria
signature.asc
Description: Message signed with OpenPGP using GPGMail
