Updated Node.js engine version and updated README.md to incorporate the deploy to Bluemix button.

Author: jeden25

README.md

@@ -1,85 +1,54 @@
-# How to Run and Deploy the Node MySQL Upload App #
+# Overview of the App #
+
+This is a Node.js app that uses the following cloud services:
+
+-   MySQL Database
+
+This app demonstrates how to connect to a MySQL database on IBM BlueMix from a Node.js app. 
+Simply upload a line-separated file of text (e.g. tweets), and it will add each line to MySQL.
+
+Give it a try! Click the button below to fork into IBM DevOps Services and deploy your own copy of this application on Bluemix.
+
+[![Deploy to Bluemix](images/deploy-button.png)](https://hub.jazz.net/code/cfui/bluemix/deploy.html?Repository=https://github.com/ibmjstart/bluemix-node-mysql-uploader.git)
+
+Enjoy! (note, it may take minute or so for the app to start)
+
+___
+
+### [Alternative] Deploying the App Via the Command-Line ###
 
-## Overview of the app ##
-
-This is a NodeJS app that uses the following cloud services:
-
--   MySQL Database
-
-This app demonstrates how to connect to a MySQL database on codename: BlueMix from a NodeJS app. 
-Simply upload a line-separated file of text (e.g. tweets), and it will add each line to MySQL.
-
-## Deploying the App and Binding the MySQL Service ##
-Multiple methods exist for interacting with the BlueMix platform. Outlined below are two of those methods:
-
-1. [Command-Line](#method-command-line) 
-2. [IBM JazzHub](#method-ibm-jazzhub)
-
-### Method: Command-Line ###
 #### Prerequisites ####
 
 Before we begin, we first need to install the [**cf**](https://github.com/cloudfoundry/cli/releases) command line tool that will be used to upload and manage your application. If you've previously installed an older version of the cf tool, make sure you are now using v6 of cf by passing it the -v flag:
 
     cf -v
 
 #### Steps ####
-In the terminal, go into the directory named **app**, and follow these steps.
+In the terminal, go into the root directory, and follow these steps.
 
 1. Login to Bluemix.
 
    | *usage:*   | `$ cf login [-a API_URL] [-o ORG] [-s SPACE]`|
    |------------|----------------------------------------------|
    | *example:* | `$ cf login -a https://api.ng.bluemix.net`   |
 
-2. Create an instance of the mySQL service, giving it a unique name in the last arguement.
+2. Create an instance of the mySQL service, giving it the name "mysql-database" in the last arguement. Note, if a different name is desired, then the manifest.yml file needs to be changed accordingly.
 
    | *usage:*   | `$ cf create-service SERVICE PLAN SERVICE_INSTANCE`|
    |------------|----------------------------------------------------|
-   | *example:* | `$ cf create-service mysql 100 mysql_NMU`          |
+   | *example:* | `$ cf create-service mysql 100 mysql-database`     |
 
-3. **From the directory that houses the _app.js_ file** (not from the root directory that contains this *README.md* file), push the app with the --no-start option so we can bind our required service before starting.  Pass the -c flag to specify the start command that should be used by CloudFoundry to run your app.  Be sure to give your app a unique app name to be used for its hostname; for instance the example below would result in http://myupload-<username>.ng.bluemix.net.
+3. From the root directory that contains this *README.md* file, push the app like below.  Be sure to give your app a unique APP_NAME to be used for its hostname. For instance the example below would result in http://myupload-&lt;username&gt;.ng.bluemix.net.
 
-   | *usage:*   | `$ cf push APP [--no-manifest] [--no-start] [-c COMMAND]`                |
-   |------------|--------------------------------------------------------------------------|
-   | *example:* | `$ cf push myupload-<username> --no-manifest --no-start -c "node app.js"`                |
-
-4. Bind the MySQL service instance to the new app
-
-   | *usage:*   | `$ cf bind-service APP SERVICE_INSTANCE`|
-   |------------|-----------------------------------------|
-   | *example:* | `$ cf bind-service myupload-<username> mysql_NMU`       |
-
-5. Start the app
-
-   | *usage:*   | `$ cf start APP`                 |
+   | *usage:*   | `$ cf push APP_NAME`                  |
    |------------|----------------------------------|
-   | *example:* | `$ cf start myupload-<username>`                 |
-   
-
-### Method: IBM JazzHub ###
-1. Browse to the JazzHub project repository located [here](https://hub.jazz.net/project/jstart/MySQL%20Upload%20App%20(Node)/overview).  Click on **Edit Code** for the project.
-2. Click on "Fork".  This will provide you with a personal copy of the code within your JazzHub project space.
-
-  ![image](images/forkProject.png)
-
-3. Located in the **app** directory of the project, rename **manifest.yml.v5** to **manifest.yml**
-
-  ![image](images/RenameManifest.png)
-
-4. Next, click on "Deploy".  This will use information within the **manifest.yml** to deploy the sample application directly into the codename: BlueMix platform.
-
-  ![image](images/Deploy.png)
-
-  You may continue to deploy changes to your BlueMix application directly from JazzHub using the "Deploy" and "Deploy As" buttons.
-
-5. Next, click on the Root Project Name and scroll to the **Manual Deployment Information** section.
-
-  ![image](images/Manage.png)
-
-  You can check the status of the app using this section. If a green filled circle is visible, you may click the Application Name shown within the section and interact with the running application.  However, if a red filled circle is displayed, you may click **Manage** and directly interact with the BlueMix User interface for further investigation and debugging.
+   | *example:* | `$ cf push myupload-<username>`  |
 
+Congratulations, the app should be running on Bluemix.
+   
+___
 
-## License ##
+### License ###
 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
 
      http://www.apache.org/licenses/LICENSE-2.0

app/package.json

@@ -2,7 +2,7 @@
   "name": "twitter-search",
   "version": "0.0.1",
   "engines": {
-        "node":     "0.8.x"
+        "node":     "0.10.x"
     },
   "scripts": {
     "start": "node app.js"

images/deploy-button.png

@@ -1,15 +1,15 @@
 ---
 declared-services:
-  mysql-node-upload:
+  mysql-database:
     type: mysql
     plan: '100'
 
 applications: #Reference http://docs.cloudfoundry.com/docs/using/deploying-apps/manifest.html
 - name: NodeMySQLUpload #Application Name. Unique to the user's Space
   memory: 256M #The maximum memory to allocate to each application instance
   instances: 1 #The number of instances of the application to start
-  path: . #Path to the application to be pushed
+  path: ./app/ #Path to the application to be pushed
   command: node app.js #The command to use to start the application
   services:
-  - mysql-node-upload #Identifier for MySQL Bound Service instance
+  - mysql-database #Identifier for MySQL Bound Service instance