×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
OK, thanks
-----Original Message-----
From: Brian P Randle [mailto:brianprandle@xxxxxxxxx]
Sent: Thursday, February 08, 2018 3:13 PM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Deploy Node?
Earlier in this thread Aaron said:
Another approach is to 'git clone...' the project to the deployment
directory and then run 'npm init' to install all the dependencies
listed in package.json. The purpose of package.json and
package-lock.json is to keep from having to store the node_modules in git.
Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces
npm would be used to download all of the node packages and dependencies that are in your package.json file, those would be the files and directories in your node_modules directory.
Those node packages could be installed globally on production first, so they would not have to be downloaded for every app. Nowadays 5mb is really a small amount of disk and managing a global directory presents other issues with managing multiple versions of the same node module.
So, copying the entire app directory including the node_modules would work fine, or pushing the app to git then using git clone in the deployment directory then getting using npm update could be used. Either way you will end up with the node_modules directory populated.
Brian Randle
midrange.com
