Update repository name from zettio to weaveworks

This commit is contained in:
Bryan Boreham committed 2015-04-08 16:35:52 +01:00
1 parent 580ffc4fa4
commit 8a82f368d0
32 files changed
+62 -62

No files matched your search

+1 -1
View File
@@ -15,7 +15,7 @@
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<a id="forkme_banner" href="https://github.com/zettio/weave">View on GitHub</a>
<a id="forkme_banner" href="https://github.com/weaveworks/weave">View on GitHub</a>
<h1 id="project_title">weave</h1>
<h2 id="project_tagline">The Docker Network</h2>
+11 -11
View File
@@ -22,11 +22,11 @@ options are described below.
## Building directly on Ubuntu
The weave git repository should be cloned into
`$GOPATH/src/github.com/zettio/weave`, in accordance with [the go
`$GOPATH/src/github.com/weaveworks/weave`, in accordance with [the go
workspace conventions](https://golang.org/doc/code.html#Workspaces):
```bash
$ WEAVE=github.com/zettio/weave
$ WEAVE=github.com/weaveworks/weave
$ git clone https://$WEAVE $GOPATH/src/$WEAVE
$ cd $GOPATH/src/$WEAVE
```
@@ -49,8 +49,8 @@ $ make
```
This will build the weave components and package them into three
Docker images (`zettio/weave`, `zettio/weavedns`, and
`zettio/weaveexec`). These are then exported (as `weave.tar`,
Docker images (`weaveworks/weave`, `weaveworks/weavedns`, and
`weaveworks/weaveexec`). These are then exported (as `weave.tar`,
`weavedns.tar` and `weaveexec.tar`).
## Building in a Docker container
@@ -60,7 +60,7 @@ that has all the prerequisites. This avoids the need to download and
install them for each build. In the `weave` directory, do:
```bash
$ sudo docker build -t zettio/weave-build build
$ sudo docker build -t weaveworks/weave-build build
```
Next we run a container based on that image. That container requires
@@ -75,7 +75,7 @@ for a way to work around this problem.
To perform a build, run:
```bash
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock zettio/weave-build https://github.com/zettio/weave.git
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock weaveworks/weave-build https://github.com/weaveworks/weave.git
```
This will clone the weave git repository, then do the build.
@@ -87,7 +87,7 @@ The container arguments are passed to `git clone`, so for example, you
can build from a forked repository and a specific branch with:
```bash
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock zettio/weave-build -b <branch name> <repo URI>
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock weaveworks/weave-build -b <branch name> <repo URI>
```
Alternatively, you might want to build from a weave source tree
@@ -97,7 +97,7 @@ to bind the bind your go workspace containing the weave repository to
passed in this case:
```bash
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock -v <host gopath>:/home/go zettio/weave-build
$ sudo docker run -v /var/run/docker.sock:/var/run/docker.sock -v <host gopath>:/home/go weaveworks/weave-build
```
This will leave the intermediate build artifacts on the host, so that
@@ -115,7 +115,7 @@ Vagrant to run VMs in.
First, check out the code:
```bash
$ git clone https://github.com/zettio/weave
$ git clone https://github.com/weaveworks/weave
$ cd weave
```
@@ -136,7 +136,7 @@ $ vagrant up
and wait for a while (don't worry, the long download and package
installation is done just once). The working directory is sync'ed with
`~/src/github.com/zettio/weave` on the VM, so you can edit files and
`~/src/github.com/weaveworks/weave` on the VM, so you can edit files and
use git and so on in the regular filesystem.
To build and run the code, you need to use the VM. To log in and build
@@ -144,7 +144,7 @@ the weave image, do
```bash
$ vagrant ssh
vm$ cd src/github.com/zettio/weave
vm$ cd src/github.com/weaveworks/weave
vm$ make
```
+1 -1
View File
@@ -6,7 +6,7 @@ layout: default
# Weave features
Weave has a few more features beyond those illustrated by the [basic
example](https://github.com/zettio/weave#example):
example](https://github.com/weaveworks/weave#example):
* [Virtual ethernet switch](#virtual-ethernet-switch)
* [Application isolation](#application-isolation)
+1 -1
View File
@@ -397,4 +397,4 @@ further.
### Further reading
More details on the inner workings of weave can be found in the
[architecture documentation](https://github.com/zettio/weave/blob/master/docs/architecture.txt).
[architecture documentation](https://github.com/weaveworks/weave/blob/master/docs/architecture.txt).
+2 -2
View File
@@ -5,12 +5,12 @@ layout: default
# weave documentation
* [Introduction and example (in README)](https://github.com/zettio/weave#readme)
* [Introduction and example (in README)](https://github.com/weaveworks/weave#readme)
* [Features](features.html)
* [Troubleshooting](troubleshooting.html)
* [Building](building.html)
* [How it works](how-it-works.html)
* [Contact information](https://github.com/zettio/weave#contact-us)
* [Contact information](https://github.com/weaveworks/weave#contact-us)
* *Installation Notes*
* [Using with boot2docker](boot2docker.html)
* [Using with systemd](systemd.html)
+1 -1
View File
@@ -64,7 +64,7 @@ context with the commands shown below. You will need to have the
sudo semanage fcontext -a -t unconfined_exec_t -f f /usr/local/bin/weave
sudo restorecon /usr/local/bin/weave
[readme]: https://github.com/zettio/weave/blob/master/README.md#installation
[readme]: https://github.com/weaveworks/weave/blob/master/README.md#installation
[connect]: http://zettio.github.io/weave/features.html#dynamic-topologies
[systemd]: http://www.freedesktop.org/wiki/Software/systemd/
[encryption]: http://zettio.github.io/weave/how-it-works.html#crypto
+3 -3
View File
@@ -8,7 +8,7 @@ layout: default
Make sure you are running the latest version - you can download it
with
docker pull zettio/weave:latest
docker pull weaveworks/weave:latest
Check the weave container logs with
@@ -116,7 +116,7 @@ from 37.157.33.76:7195.
The 'Routes' section summarised the information for deciding how to
route packets between peers, which is mostly of interest when the
weave network is not fully connected. See the
[architecture documentation](https://raw.githubusercontent.com/zettio/weave/master/docs/architecture.txt)
[architecture documentation](https://raw.githubusercontent.com/weaveworks/weave/master/docs/architecture.txt)
for a full explanation.
The 'Reconnects' section lists peers that this router is aware of, but is
@@ -126,7 +126,7 @@ connecting again.
Finally, status information from weave DNS is included. In this example,
the DNS container has not been launched so no status information is
available (see the [WeaveDNS README](https://github.com/zettio/weave/blob/master/weavedns/README.md)
available (see the [WeaveDNS README](https://github.com/weaveworks/weave/blob/master/weavedns/README.md)
for more information).
### <a name="list-attached-containers"></a>List attached containers