Community
Using the node.js cfenv package to make your life easier
July 17, 2014 | Written by: Patrick Mueller
Share this post:
I’ve just put together a little Bluemix application for node.js – bluemix-service-switcher – which shows how to access service information using the cfenv package.
This sample, and the cfenv
package, should also work fine on any Cloud Foundry-based PaaS.
cfenv
provides a number of functions to deal with the VCAP_SERVICES
and VCAP_APPLICATION
environment variables.
You will never have to JSON.parse()
them again!
Almost every server I write uses the following little snippet to start the server:
<code>var app = express()
var appEnv = cfenv.getAppEnv()...
app.listen(appEnv.port, appEnv.bind, function() {
util.log("server starting on " + appEnv.url)
})
</code>
This will start your server on the right port, bind to right address, and print the url of the server when it’s started.
cfenv
also works when you run locally, on your development machine, and provides appropriate default values when running in that environment.
The service-switcher
application makes use of cfenv
‘s functions to show how easy it is to access your bound services, and for your app be flexible about the services it binds to.
We’ve Moved! The IBM Cloud Blog Has a New URL
In an effort better integrate the IBM Cloud Blog with the IBM Cloud web experience, we have migrated the blog to a new URL: www.ibm.com/cloud/blog.
Two Tutorials: Plan, Create, and Update Deployment Environments with Terraform
Multiple environments are pretty common in a project when building a solution. They support the different phases of the development cycle and the slight differences between the environments, like capacity, networking, credentials, and log verbosity. These two tutorials will show you how to manage the environments with Terraform.
Transforming Customer Experiences with AI Services (Part 1)
This is an experience from a recent customer engagement on transcribing customer conversations using IBM Watson AI services.