github/weave-scope
1
0
Fork 0
mirror of https://github.com/weaveworks/scope.git synced 2026-07-28 17:51:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

remove space to match weave net convention

Browse Source
This commit is contained in:
abuehrle
2017-08-16 12:01:43 -05:00
parent 009976fa9a
commit b3823399fc
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
site/building.md
View File

@@ -36,7 +36,7 @@ Similarly the frontent client tests can be run via:
make client-test
> **Note:** The tools from `make deps` depend on a local install of
>**Note:** The tools from `make deps` depend on a local install of
[Go](https://golang.org).
## <a name="debugging"></a>Debugging

2
site/installing.md
View File

@@ -47,7 +47,7 @@ Where,
* `<VM name>` is the name you gave to your virtual machine with docker-machine.
> **Note:** Scope allows anyone with access to the user interface, control over your containers. As such, the Scope app endpoint (port 4040) should not be made accessible on the Internet. Also traffic between the app and the probe is insecure and should not traverse the Internet. This means that you should either use the private / internal IP addresses of your nodes when setting it up, or route this traffic through Weave Net. Put Scope behind a password, by using an application like [Caddy](https://github.com/mholt/caddy) to protect the endpoint and by making port 4040 available to localhost with Caddy proxying it. Or you can skip these steps, and just use Weave Cloud to manage the security for you.
>**Note:** Scope allows anyone with access to the user interface, control over your containers. As such, the Scope app endpoint (port 4040) should not be made accessible on the Internet. Also traffic between the app and the probe is insecure and should not traverse the Internet. This means that you should either use the private / internal IP addresses of your nodes when setting it up, or route this traffic through Weave Net. Put Scope behind a password, by using an application like [Caddy](https://github.com/mholt/caddy) to protect the endpoint and by making port 4040 available to localhost with Caddy proxying it. Or you can skip these steps, and just use Weave Cloud to manage the security for you.
### <a name="docker-weave-cloud"></a>Using Weave Cloud

6
site/plugins.md
View File

@@ -34,13 +34,13 @@ Official Weave Scope plugins can be found at [Weaveworks Plugins](https://github
* Number of HTTP requests per seconds.
* Number of HTTP responses code per second (per code).
> **Note:** The HTTP Statistics plugin requires a [recent kernel version with ebpf support](https://github.com/iovisor/bcc/blob/master/INSTALL.md#kernel-configuration) and it will not compile on [dlite](https://github.com/nlf/dlite) or on boot2docker hosts.
>**Note:** The HTTP Statistics plugin requires a [recent kernel version with ebpf support](https://github.com/iovisor/bcc/blob/master/INSTALL.md#kernel-configuration) and it will not compile on [dlite](https://github.com/nlf/dlite) or on boot2docker hosts.
* [Traffic Control](https://github.com/weaveworks-plugins/scope-traffic-control): This plugin allows you to modify latency and packet loss for a specific container via controls from the container's detailed view in the Scope user interface.
* [Volume Count](https://github.com/weaveworks-plugins/scope-volume-count): This plugin (written in Python) requests the number of mounted volumes for each container, and provides a container-level count.
> **Note:**Installed and running plugins are shown in the list of `PLUGINS` in the bottom right of the Scope UI.
>**Note:**Installed and running plugins are shown in the list of `PLUGINS` in the bottom right of the Scope UI.
## <a id="plugins-internals"></a>How Plugins Communicate with Scope
@@ -88,7 +88,7 @@ For example:
}
```
> **Note:** The `Plugins` section includes exactly one plugin description that displays in the UI. The other plugin fields are:
>**Note:** The `Plugins` section includes exactly one plugin description that displays in the UI. The other plugin fields are:
* `id` - checks for duplicate plugins. It is required.
* `label` - a human readable label displayed in the UI. It is required.