NeedToNode Recap: Using NodeSource on Cloud Foundry
Deploying Node.js applications to a cloud platform correctly can be a bit of a daunting task. In our December #NeedToNode webinar with Patrick Mueller, we got the awesome chance to look at how to do it easily and effectively on Cloud Foundry. Here's a quick recap of the webinar, with some takeaways, resources, and people of interest.
Top 3 Takeaways
-
Add
node_modulesthe .cfignore file to speed up deployment -
Use the
cfenvmodule to get deep access into the Cloud Foundry environment -
Deploy N|Solid to Cloud Foundry by simply using the N|Solid buildpack
Video
Webinar Recap
Cloud Foundry is a PaaS product that has some striking similarities to Heroku, including some of the core concepts and key terminology used. Cloud Foundry is an open-source project, and a part of the Cloud Foundry Foundation. There are also several paid options for hosting a Cloud Foundry instance from companies like Pivotal, GE, and CenturyLink.
You can spin up just about any Node.js application inside of Cloud Foundry with a few basic configuration steps, mainly in the mainifest.yml configuration file that's part of Cloud Foundry. These changes will allow you to speedily deploy and scale any Node.js application within Cloud Foundry to in production quickly and easily.
NodeSource now has an N|Solid Buildpack to deploy on Cloud Foundry that serves a drop-in replacement for the Node.js buildpack. This buildpack allows you to run your Node.js application on N|Solid with no modifications, as-per usual. To get set up, you’ll simply need to point to the N|Solid buildpack repo as your Cloud Foundry buildpack, and add the nsolid-storage service to your manifest.yml.