Rename node to nodejs

Author: Tobias Fuhrimann

bind-service.html.md.erb

@@ -24,10 +24,10 @@ This creates a small MongoDB database for you which we now have to bind to our a
 Let's bind the new service to our existing application:
 
 <pre class="terminal">
-$ cf bind-service my-node-app my-mongodb
-Binding service my-mongodb to app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf bind-service my-nodejs-app my-mongodb
+Binding service my-mongodb to app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
-TIP: Use 'cf restage my-node-app' to ensure your env variable changes take effect
+TIP: Use 'cf restage my-nodejs-app' to ensure your env variable changes take effect
 </pre>
 
 <p class="note">
@@ -37,7 +37,7 @@ TIP: Use 'cf restage my-node-app' to ensure your env variable changes take effec
 After that we restage the application as suggested so that it includes the new credentials in its environment variables:
 
 <pre class="terminal">
-$ cf restage my-node-app
+$ cf restage my-nodejs-app
 Restaging app my-app in org MyOrg / space MySpace as [email protected]...
 -----> Downloaded app package (8.0K)
 -------> Buildpack version 1.5.8
@@ -50,7 +50,7 @@ Now we want to consume our new MongoDB from within our application. Use npm to a
 
 <pre class="terminal">
 $ npm install --save mongoose
-cf-sample-app-node@0.0.0 /.../cf-sample-app-node
+cf-sample-app-nodejs@0.0.0 /.../cf-sample-app-nodejs
 └─┬ [email protected]
   ├── [email protected]
   ├── [email protected]
@@ -189,7 +189,7 @@ if (process.env.VCAP_SERVICES) {
 checks if the app is running in the cloud. If not, it falls back to the default local MongoDB url. This allows you to run your app locally as well as in the cloud without having to configure anything differently. So let's push it to the cloud using
 
 <pre class="terminal">
-$ cf push my-node-app
+$ cf push my-nodejs-app
 </pre>
 
 You can access other services like Redis or MariaDB in a similar matter, simply by binding them to your app and accessing them through the environment variables.

dependencies.html.md.erb

@@ -11,7 +11,7 @@ The demo app you deployed already has a `package.json`, and it looks something l
 
 ```json
 {
-  "name": "cf-sample-app-node",
+  "name": "cf-sample-app-nodejs",
   "description": "A sample Node.js application to run on Cloud Foundry out of the box",
   "keywords": [
     "cloud-foundry"
@@ -37,10 +37,10 @@ The demo app you deployed already has a `package.json`, and it looks something l
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/swisscom/cf-sample-app-node.git"
+    "url": "https://github.com/swisscom/cf-sample-app-nodejs.git"
   },
   "bugs": {
-    "url": "https://github.com/swisscom/cf-sample-app-node/issues"
+    "url": "https://github.com/swisscom/cf-sample-app-nodejs/issues"
   }
 }
 ```
@@ -51,7 +51,7 @@ Run this command in your local directory to install the dependencies, preparing
 
 <pre class="terminal">
 $ npm install
-cf-sample-app-node@0.0.0 /.../cf-sample-app-node
+cf-sample-app-nodejs@0.0.0 /.../cf-sample-app-nodejs
 ├─┬ [email protected]
 │ ├── [email protected]
 │ ├── [email protected]

deploy.html.md.erb

@@ -10,18 +10,18 @@ In this step you will deploy the app to <%= vars.product_full %>.
 Push your app to the cloud by executing the following command and replacing the "my-random-hostname" with your own hostname. This will be part of the URL your app will be reached at and it has to be globally unique so be creative. The `-m 128M` tells Cloud Foundry to use 128MB of memory for our app which should be plenty.
 
 <pre class="terminal">
-$ cf push my-node-app -m 128M -n my-random-hostname
-Creating app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf push my-nodejs-app -m 128M -n my-random-hostname
+Creating app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 
 Creating route my-random-hostname.scapp.io...
 OK
 
-Binding my-random-hostname.scapp.io to my-node-app...
+Binding my-random-hostname.scapp.io to my-nodejs-app...
 OK
 
-Uploading my-node-app...
-Uploading app files from: /.../cf-sample-app-node
+Uploading my-nodejs-app...
+Uploading app files from: /.../cf-sample-app-nodejs
 Uploading 6.1K, 17 files
 Done uploading
 OK
@@ -40,8 +40,8 @@ buildpack: node.js 1.5.8
 The application is now deployed. Ensure that the app is running:
 
 <pre class="terminal">
-$ cf app my-node-app
-Showing health and status for app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf app my-nodejs-app
+Showing health and status for app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 
 requested state: started

environment.html.md.erb

@@ -10,17 +10,17 @@ owner: Tobias Fuhrimann
 At runtime, environment variables are exposed to the application through its environment. You can use these for example to run Node.js in production mode setting the `NODE_ENV` environment variable.
 
 <pre class="terminal">
-$ cf set-env my-node-app NODE_ENV production
-Setting env variable 'NODE_ENV' to 'production' for app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf set-env my-nodejs-app NODE_ENV production
+Setting env variable 'NODE_ENV' to 'production' for app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 TIP: Use 'cf restage' to ensure your env variable changes take effect
 </pre>
 
 Then restage your app as suggested using
 
 <pre class="terminal">
-$ cf restage my-node-app
-Restaging app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf restage my-nodejs-app
+Restaging app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 -----> Downloaded app package (8.0K)
 -----> Downloaded app buildpack cache (2.3M)
 -------> Buildpack version 1.5.8

index.html.md.erb

@@ -13,6 +13,10 @@ The tutorial assumes that you have an <a href="https://console.developer.swissco
 
 Furthermore, you must have a first Cloud Foundry <a href="../concepts/roles.html#orgs" target="_blank">Organization</a> and <a href="../concepts/roles.html#spaces" target="_blank">Space</a> to push your apps to. In case you don't have that yet, please follow the <a href="https://console.developer.swisscom.com" target="_blank">tutorials in the web console</a> before returning here.
 
+<p class="note">
+  <strong>Note</strong>: In case you are stuck during the tutorial, you can always check out the <a href="https://github.com/swisscom/cf-sample-app-nodejs/tree/final-result" target="_blank"><code>final-result</code></a> branch of the sample app repo to see what your code should look like.
+</p>
+
 <div style="text-align:center;margin:3em;">
   <a href="./set-up.html" class="btn btn-primary">I'm ready to start</a>
 </div>

logs.html.md.erb

@@ -10,8 +10,8 @@ owner: Tobias Fuhrimann
 View information about your running app using one of the logging commands, `cf logs`:
 
 <pre class="terminal">
-$ cf logs my-node-app
-Connected, tailing logs for app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf logs my-nodejs-app
+Connected, tailing logs for app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 
 2016-03-30T16:37:06.39+0200 [App/0]      OUT GET / 200 1.756 ms - 212
 2016-03-30T16:37:06.39+0200 [RTR/1]      OUT my-random-hostname.scapp.io - [30/03/2016:14:37:06 +0000] "GET / HTTP/1.1" 200 0 212 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36" 195.65.130.2:61671 x_forwarded_for:"-" x_forwarded_proto:"http" vcap_request_id:f1ac25ce-2ca5-4538-59c5-83d58de55766 response_time:0.005294073 app_id:c98d5025-1bc9-46aa-8bba-51f55f7f2599
@@ -24,7 +24,7 @@ Press `Ctrl+C` to stop streaming the logs.
 You can use
 
 <pre class="terminal">
-$ cf logs my-node-app --recent
+$ cf logs my-nodejs-app --recent
 </pre>
 
 to get the most recent logs.

manifest.html.md.erb

@@ -10,7 +10,7 @@ It's tedious to keep having to specify the app name and other variables each tim
 ```yaml
 ---
 applications:
-- name: my-node-app
+- name: my-nodejs-app
   memory: 128MB
   instances: 1
 
@@ -23,7 +23,7 @@ applications:
     NODE_ENV: production
 ```
 
-The file tells Cloud Foundry that this is an application with the name `my-node-app` and the specifications made above. This means that from now on, you'll be able to push your App with the simple command:
+The file tells Cloud Foundry that this is an application with the name `my-nodejs-app` and the specifications made above. This means that from now on, you'll be able to push your App with the simple command:
 
 <pre class="terminal">
 $ cf push

prepare.html.md.erb

@@ -9,8 +9,8 @@ In this step, you will prepare a simple application that can be deployed.
 Execute the following commands to clone the sample application:
 
 <pre class="terminal">
-$ git clone https://github.com/swisscom/cf-sample-app-node.git
-$ cd cf-sample-app-node
+$ git clone https://github.com/swisscom/cf-sample-app-nodejs.git
+$ cd cf-sample-app-nodejs
 </pre>
 
 You now have a functioning git repository that contains a simple <a href="https://expressjs.com/" target="_blank">Express</a> application as well as a `package.json` file, which is used by Node’s dependency manager npm.

push-changes.html.md.erb

@@ -34,7 +34,7 @@ Visiting your application at <a href="http://localhost:3000" target="_blank">htt
 Now deploy. All you need to do is `cf push` again:
 
 <pre class="terminal">
-$ cf push my-node-app
+$ cf push my-nodejs-app
 </pre>
 
 Finally, check that everything is working by visiting your app's URL from your web browser.

run-locally.html.md.erb

@@ -10,7 +10,7 @@ Now start your application locally using the `npm start` command:
 <pre class="terminal">
 $ npm start
 
-&gt; cf-sample-app-node@0.0.0 start /.../cf-sample-app-node
+&gt; cf-sample-app-nodejs@0.0.0 start /.../cf-sample-app-nodejs
 &gt; node ./bin/www
 </pre>
 

scale.html.md.erb

@@ -10,8 +10,8 @@ Currently, your app is running as a single instance with 128MB of memory.
 You can check how many instances are running and how much memory they have using the `cf scale` command:
 
 <pre class="terminal">
-$ cf scale my-node-app
-Showing current scale of app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf scale my-nodejs-app
+Showing current scale of app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 
 memory: 128M
@@ -26,8 +26,8 @@ By default, your app is deployed as one instance. Each instance runs in a separa
 Scaling an application horizontally on <%= vars.product_full %> is equivalent to changing the number of instances that are running. Scale the number of instances to 3:
 
 <pre class="terminal">
-$ cf scale my-node-app -i 3
-Scaling app my-node-app in org MyOrg / space MySpace as [email protected]...
+$ cf scale my-nodejs-app -i 3
+Scaling app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 </pre>
 
@@ -36,11 +36,11 @@ OK
 Scaling an application vertically on <%= vars.product_full %> is equivalent to changing the amount of memory each instance has. Scale the amount of memory to 256MB:
 
 <pre class="terminal">
-$ cf scale my-node-app -m 256M
+$ cf scale my-nodejs-app -m 256M
 
-This will cause the app to restart. Are you sure you want to scale my-node-app?&gt; yes
+This will cause the app to restart. Are you sure you want to scale my-nodejs-app?&gt; yes
 
-Scaling app my-node-app in org MyOrg / space MySpace as [email protected]...
+Scaling app my-nodejs-app in org MyOrg / space MySpace as [email protected]...
 OK
 
 ...