Getting Started with Node.js on Cloud Foundry
summary
Node.js on Cloud Foundry uses the Node buildpack to detect package.json, run npm install during staging, and honor package.json engines plus manifest.yml; the buildpack recently adds Node 8 support but defaults can lag (example default was 4.8.x), so pin the engine. Default CF resources are 256 MB memory / 512 MB disk; typical Node apps work well at 512 MB memory and 128 MB disk and scale horizontally rather than by threads. CF supports Docker images via the diego_docker feature flag but requires accessible registries with valid SSL. Use cf push and the cfenv helper to mirror VCAP locally.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:32Node.js benefits on Cloud Foundry
- 5:58Node.js build pack basics
- 9:52Recommended Node.js versions and settings
- 12:22Port handling in Cloud Foundry
- 13:26Node modules and deployment
- 16:15Preparing app for Cloud Foundry
- 18:03Live demo of CF push
- 20:12Docker containers in Cloud Foundry
- 24:27Deploying with Docker images
- 27:38Why containers fit Node.js
- 28:10Q&A and closing remarks
related talks
32mCloud Foundry for Everyone!
31mDeploy Your First Cloud Foundry App
29m10 common errors when pushing applications to CloudFoundry
27mCloud Native Landscape for Node.js Developers
35mBuilding Security In: Using Cloud Foundry to Secure CF Apps
16mComing Soon to a Cloud Near You: Multiple Buildpack Support
26mCloud Native Buildpacks: Containers for Everyone
41mBoF: Getting Started with Node.js