updating README notes to match MongoDB usage info

Author: ryanj

README.md

@@ -1,22 +1,22 @@
 # Map of National Parks and Historic Sites
-*powered by RESTify, PostGIS, and Leaflet maps*
+*powered by Restify, MongoDB, and Leaflet maps*
 
-A basic instant mapping demo using PostGIS, node-restify, LeafLet Maps and map tiles from Stamen, to visualize the locations of major National Parks and Historic Sites.
+A basic instant mapping demo using MongoDB, node-restify, LeafLet Maps and map tiles from Stamen, to visualize the locations of major National Parks and Historic Sites.
 
-<a href='http://nodegis-shifter.rhcloud.com/'><img src='https://www.openshift.com/sites/default/files/Parks_preview.png'/></a>
+<a href='http://parks-shifter.rhcloud.com/'><img src='https://www.openshift.com/sites/default/files/Parks_preview.png'/></a>
 
 Related post on OpenShift.com: [https://www.openshift.com/blogs/instant-mapping-applications-with-postgis-and-nodejs](https://www.openshift.com/blogs/instant-mapping-applications-with-postgis-and-nodejs)
 
 ## Instant Provisioning on OpenShift
 To deploy a clone of this application using the [`rhc` command line tool](http://rubygems.org/gems/rhc), type:
 
-    rhc app create parks nodejs-0.10 postgresql-9.2 --from-code=https://github.com/ryanj/restify-postGIS.git
+    rhc app create parks nodejs-0.10 mongodb-2.2 --from-code=https://github.com/ryanj/restify-mongodb-parks.git
 
-Or, [link to a web-based **clone+deploy**](https://openshift.redhat.com/app/console/application_type/custom?name=parks&cartridges%5B%5D=nodejs-0.10&cartridges%5B%5D=postgresql-9.2&initial_git_url=https%3A%2F%2Fgithub.com%2Fryanj%2Frestify-postGIS.git) on [OpenShift Online](http://OpenShift.com) or [your own open cloud](http://openshift.github.io): 
+Or, [link to a web-based **clone+deploy**](https://openshift.redhat.com/app/console/application_type/custom?name=parks&cartridges%5B%5D=nodejs-0.10&cartridges%5B%5D=mongodb-2.2&initial_git_url=https%3A%2F%2Fgithub.com%2Fryanj%2Frestify-mongodb-parks.git) on [OpenShift Online](http://OpenShift.com) or [your own open cloud](http://openshift.github.io): 
 
-    https://openshift.redhat.com/app/console/application_type/custom?name=parks&cartridges%5B%5D=nodejs-0.10&cartridges%5B%5D=postgresql-9.2&initial_git_url=https%3A%2F%2Fgithub.com%2Fryanj%2Frestify-postGIS.git
+    https://openshift.redhat.com/app/console/application_type/custom?name=parks&cartridges%5B%5D=nodejs-0.10&cartridges%5B%5D=mongodb-2.2&initial_git_url=https%3A%2F%2Fgithub.com%2Fryanj%2Frestify-mongodb-parks.git
 
-A live demo is available at: [http://nodegis-shifter.rhcloud.com/](http://nodegis-shifter.rhcloud.com/)
+A live demo is available at: [http://parks-shifter.rhcloud.com/](http://parks-shifter.rhcloud.com/)
 
 ## Local Development
 Before you spin up a local server, you'll need a copy of the source code, and an installation of [nodejs](http://nodejs.org/).
@@ -30,7 +30,7 @@ OpenShift will automatically resolve `package.json` dependencies for hosted appl
     npm install
 
 ### port-forwarding for local access to your remote db
-You can set up your own postgreSQL database for local development.  But, OpenShift provides a great way to get connected to your fully hosted and configured PostgreSQL database in mere seconds.  
+You can set up your own MongoDB database for local development.  But, OpenShift provides a great way to get connected to your fully hosted and configured DB in mere seconds 
 
 The `rhc port-forward` command establishes a local connection to your hosted database, where your DB permissions, table schema, and map data have already been initialized.  
 
@@ -39,19 +39,19 @@ The command output will provides your local connection details:
     Service    Local               OpenShift
     ---------- -------------- ---- ----------------
     node       127.0.0.1:8080  =>  127.5.199.1:8080
-    postgresql 127.0.0.1:5433  =>  127.5.199.2:5432
+    mongodb    127.0.0.1:27017 =>  127.5.199.2:27017
 
     Press CTRL-C to terminate port forwarding
 
-Make a note of the *local* postgresql IP address and port number, and leave the command running (in order to keep the connection open).  We will need to use these values in the next step.
+Make a note of the *local* MongoDB IP address and port number, and leave the command running (in order to keep the connection open).  We will need to use these values in the next step.
 
 ### Basic Configuration
 This app uses the `config` npm module, which loads it's configuration details from the `config/defaults.json` file.  This configuration takes advantage of several environment variables whenever they are available.  On OpenShift, many of these values are automatically provided for your application by their associated cartridge add-on service:
 
     module.exports = {
       port: process.env.PORT || process.env.OPENSHIFT_NODEJS_PORT || 3000,
       ip: process.env.OPENSHIFT_NODEJS_IP || '127.0.0.1',
-      pg_config: process.env.OPENSHIFT_POSTGRESQL_DB_URL || 'postgresql://127.0.0.1:5432',
+      db_config: process.env.OPENSHIFT_MONGODB_DB_URL || 'mongodb://127.0.0.1:27017',
       table_name: process.env.OPENSHIFT_APP_NAME || 'parks'
     }
 
@@ -66,26 +66,26 @@ You can find this information by running `env` while connected to your OpenShift
 ### Environment Variables
 Now, set your `OPENSHIFT_POSTGRESQL_DB_URL` environment variable, substituting your own `DB_USERNAME`, `DB_PASSWORD`, `LOCAL_DB_IP`, and `LOCAL_DB_PORT`:
 
-    export OPENSHIFT_POSTGRESQL_DB_URL="postgres://DB_USERNAME:DB_PASSWORD@LOCAL_DB_IP:LOCAL_DB_PORT"
+    export OPENSHIFT_MONGODB_DB_URL="mongodb://DB_USERNAME:DB_PASSWORD@LOCAL_DB_IP:LOCAL_DB_PORT"
 
 My application's command ended up looking like this:
 
-    export OPENSHIFT_POSTGRESQL_DB_URL="postgres://admin32jk510:[email protected]:5433"
+    export OPENSHIFT_MONGODB_DB_URL="mongodb://admin32jk510:[email protected]:5433"
 
-This app also expects to use a Postgres `table_name` that matches your application's name (as defined within OpenShift).  When running this application on OpenShift, the `OPENSHIFT_APP_NAME` environment variable will be automatically populated.  If you didn't name your application "parks" (the default value for this option), then you will likely need to set an extra environment variable containing your table name in your local dev environment:
+This app also expects to use a MongoDB collection name (`table_name`) that matches your application's name (as defined within OpenShift).  When running this application on OpenShift, the `OPENSHIFT_APP_NAME` environment variable will be automatically populated.  If you didn't name your application "parks" (the default value for this option), then you will likely need to set an extra environment variable containing your table name in your local dev environment:
 
     export OPENSHIFT_APP_NAME=parks
 
 #### Testing your connection
-You can verify that your port-forwarding tunnel is active, and that your environment variables are configured correctly by using them to make a DB connection using the `psql` command-line client:
+You can verify that your port-forwarding tunnel is active, and that your environment variables are configured correctly by using them to make a DB connection using the `mongo` command-line client:
 
-    psql $OPENSHIFT_POSTGRESQL_DB_URL/$OPENSHIFT_APP_NAME
+    mongo $OPENSHIFT_MONGODB_DB_URL/$OPENSHIFT_APP_NAME
 
 This should provide a direct connection to your OpenShift-hosted database instance.
 
 Here you can verify that your application's [automatic database import procedures](https://www.openshift.com/blogs/instant-mapping-applications-with-postgis-and-nodejs#bootstrapping) have successfully completed, by checking the number of records in our DB table:
 
-    select count(*) from parks;
+    db.parks.count;
 
 The result should be `547`.  As usual, if you named your application something other than `parks`, you'll need to modify above the command to match your particular configuration.