Robert HerholdandSoam Vasani
9bdaf3c74e
Upgrades the node environment to NodeJS 7.6.0. Functions can now use async/await and promises; they can return a promise instead of using a callback. The change preserves compatibility with the callback style. * Upgrade node environment to Node.js 7.6.0+ * Bump package version * Preserve compatibility for callbacks * Cleanup * Re-add hello callback example * Make sure not returning won't blow everything up * Update stock example with request promise
Fission: NodeJS Environment
This is the NodeJS environment for Fission.
It's a Docker image containing a NodeJS runtime, along with a dynamic loader. A few common dependencies are included in the package.json file.
Customizing this image
To add package dependencies, edit package.json to add what you need, and rebuild this image (instructions below).
You also may want to customize what's available to the function in its
request context. You can do this by editing server.js (see the
comment in that file about customizing request context).
Rebuilding and pushing the image
You'll need access to a Docker registry to push the image: you can sign up for Docker hub at hub.docker.com, or use registries from gcr.io, quay.io, etc. Let's assume you're using a docker hub account called USER. Build and push the image to the the registry:
docker build -t USER/nodejs-env . && docker push USER/nodejs-env
Using the image in fission
You can add this customized image to fission with "fission env create":
fission env create --name nodejs --image USER/nodejs-env
Or, if you already have an environment, you can update its image:
fission env update --name nodejs --image USER/nodejs-env
After this, fission functions that have the env parameter set to the same environment name as this command will use this environment.