Update readme with instructions around deploying through marathon, fix urls in package.json

Author: tayzlor

README.md

@@ -50,6 +50,15 @@ so you don't necessarily need a working Mesos Cluster. For that we are using
 
 ## Usage
 
+### Deploying the UI through Marathon
+
+Edit ```marathon.json``` and replace ```MESOS_ENDPOINT``` with the URL of your
+Mesos master, and adjust the cpu or memory if desired, and then execute -
+
+```
+curl -X POST -HContent-Type:application/json -d @marathon.json http://MARATHON_ENDPOINT:8080/v2/apps
+```
+
 ### Building the Docker container
 
 ```

marathon.json

@@ -4,8 +4,7 @@
   "cpus": 0.1,
   "mem": 512,
   "env": {
-    "MESOS_ENDPOINT": "http://127.0.0.1:5050",
-    "MARATHON_ENDPOINT": "http://127.0.0.1:8080"
+    "MESOS_ENDPOINT": "http://127.0.0.1:5050"
   },
   "labels": {
     "DCOS_PACKAGE_NAME": "mesos-ui",

package.json

@@ -4,11 +4,12 @@
   "description": "A UI for Mesos built on React.JS.",
   "license": "MIT",
   "bugs": {
-    "url": "https://github.com/capgemini/react-scaffold/issues"
+    "url": "https://github.com/capgemini/mesos-ui/issues"
   },
-  "homepage": "https://github.com/capgemini/react-scaffold",
+  "homepage": "https://github.com/capgemini/mesos-ui",
   "keywords": [
     "mesos",
+    "apache",
     "ui",
     "react"
   ],