A Cloud Foundry buildpack for Node based apps.
This is based on the [Heroku buildpack] (https://github.com/heroku/heroku-buildpack-nodejs).
Additional documentation can be found at the CloundFoundry.org.
This buildpack will get used if you have a package.json file in your project's root directory.
cf push my_app -b https://github.com/cloudfoundry/buildpack-nodejs.gitThe primary purpose of extending the heroku buildpack is to cache system dependencies for firewalled or other non-internet accessible environments. This is called 'offline' mode.
'offline' buildpacks can be used in any environment where you would prefer the system dependencies to be cached instead of fetched from the internet.
The list of what is cached is maintained in bin/package.
Using cached system dependencies is accomplished by overriding curl during staging. See bin/compile
In offline mode we use the semver node_module (as opposed to http://semver.io) to resolve the correct node version. The semver.io service has an additional preference for stable versions not present in the node module version. We wrap the node module using lib/version_resolver.js to add back this functionality.
Offline mode expects each app to use npm to manage dependencies. npm install will vendor your dependencies into /node_modules.
-
Make sure you have fetched submodules
git submodule update --init
-
Build the buildpack
```bash
bin/package [ online | offline ]
```
-
Use in Cloud Foundry
Upload the buildpack to your Cloud Foundry and optionally specify it by name
cf create-buildpack custom_node_buildpack node_buildpack-offline-custom.zip 1 cf push my_app -b custom_node_buildpack
See the Machete CF buildpack test framework for more information.
- Fork the project
- Submit a pull request
Open an issue on this project
The project backlog is on Pivotal Tracker