From 091adb79c052e2cbc617435274a53a1d00fb3226 Mon Sep 17 00:00:00 2001 From: abuehrle Date: Thu, 30 Jun 2016 16:24:55 -0500 Subject: [PATCH 1/3] removed boot2docker reference --- site/installing.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/site/installing.md b/site/installing.md index 1a84036f6..a6db5b981 100644 --- a/site/installing.md +++ b/site/installing.md @@ -37,9 +37,13 @@ This script downloads and runs a recent Scope image from the Docker Hub. Scope n After it’s been launched, open your browser to `http://localhost:4040`. -> **Note:** If you're using boot2docker, replace localhost with the output of boot2docker IP. +If you are using docker-machine, replace localhost with the IP after you've run, `docker-machine ip `. -> Scope allows anyone with access to the UI control over your containers: as such, the Scope app endpoint (port 4040) should not be made accessible on the Internet. Additionally traffic between the app and the probe is currently insecure and should also not traverse the Internet. +Where, + + * `` is the name you gave to your virtual machine with docker-machine. + +> **Note:** Scope allows anyone with access to the UI control over your containers: as such, the Scope app endpoint (port 4040) should not be made accessible on the Internet. Additionally traffic between the app and the probe is currently insecure and should also not traverse the Internet. ###Using Weave Cloud @@ -53,11 +57,11 @@ Then, install Scope onto your local Docker machine and start using Weave Cloud: Where, -* `--service-token=` is the token that you obtained when you signed up. +* `--service-token=` is the token you obtained after you signed up for Weave Cloud. This script downloads and runs a recent Scope docker image from the Docker Hub. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it also doesn’t depend on Weave Net. -After Scope has been launched, open your web browser to [https://cloud.weave.works](https://cloud.weave.works) and login. Click 'View Instance' in the top right-hand corner to see the Scope user interface. +After Scope has been launched, open your web browser to [https://cloud.weave.works](https://cloud.weave.works) and login. Click 'View Instance' in the top right-hand corner to see the Scope user interface. ### Weave Net and Scope From 004b0e618d32d3eab85627554adf07fea059d36e Mon Sep 17 00:00:00 2001 From: abuehrle Date: Sun, 3 Jul 2016 09:29:29 -0500 Subject: [PATCH 2/3] added url output --- site/installing.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/site/installing.md b/site/installing.md index a6db5b981..c1d102f05 100644 --- a/site/installing.md +++ b/site/installing.md @@ -35,7 +35,7 @@ To install Scope onto your local Docker machine in standalone mode, run the foll This script downloads and runs a recent Scope image from the Docker Hub. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it also doesn’t depend on Weave Net. -After it’s been launched, open your browser to `http://localhost:4040`. +After it’s been launched, open your browser to `http://localhost:4040`. The URLs where you can point your browser are also printed by `scope launch`. If you are using docker-machine, replace localhost with the IP after you've run, `docker-machine ip `. @@ -129,7 +129,7 @@ To install Scope on your local Docker machine with Weave Cloud and use Docker Co Where, -* `SCOPE_SERVICE_TOKEN=` is the token that you obtained when you signed up. +* `SCOPE_SERVICE_TOKEN=` is the token you obtained after you signed up for Weave Cloud. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it also doesn’t depend on Weave Net. @@ -236,7 +236,7 @@ To get the latest release of Scope deployed onto a Kubernetes cluster, run the f Where, -* `service-token=` is the token that you obtained when you signed up with Weave Cloud. +* `service-token=` is the token you obtained after you signed up for Weave Cloud. > **Note:**The `--validate=false` flag is currently required due to a bug in Kubernetes (see [kubernetes/kubernetes#24089](https://github.com/kubernetes/kubernetes/issues/24089) for details. @@ -274,8 +274,7 @@ For step by step instructions on how to configure the stack, see: [Install Weave ##Installing Scope on minimesos -The [minimesos](https://github.com/ContainerSolutions/minimesos) project enables you to run an Apache Mesos cluster on a single -machine, which makes it very easy to develop Mesos frameworks. +The [minimesos](https://github.com/ContainerSolutions/minimesos) project enables you to run an Apache Mesos cluster on a single machine, which makes it very easy to develop Mesos frameworks. By default, Weave Scope is included in the minimesos cluster, and can be accessed at `http://172.17.0.1:4040/`. From 70fa0fb79baf529c2e4218144f79ae892b2fc6fe Mon Sep 17 00:00:00 2001 From: Anita Buehrle Date: Thu, 7 Jul 2016 18:03:06 -0500 Subject: [PATCH 3/3] fixed up some awkwardness --- site/installing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site/installing.md b/site/installing.md index c1d102f05..d784a6776 100644 --- a/site/installing.md +++ b/site/installing.md @@ -35,9 +35,9 @@ To install Scope onto your local Docker machine in standalone mode, run the foll This script downloads and runs a recent Scope image from the Docker Hub. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it also doesn’t depend on Weave Net. -After it’s been launched, open your browser to `http://localhost:4040`. The URLs where you can point your browser are also printed by `scope launch`. +After it’s been launched, open your browser to `http://localhost:4040`. The URLs are also displayed to you in the terminal window after Weave Scope was launched. -If you are using docker-machine, replace localhost with the IP after you've run, `docker-machine ip `. +If you are using docker-machine, you can find the IP by running, `docker-machine ip `. Where,