Merge branch 'latest_release_doc_updates' into 1.2
This commit is contained in:
commit
ca6bce3820
4 files changed
+19
-14
No files matched your search
@@ -327,8 +327,6 @@ func (peers *Peers) ApplyUpdate(update []byte) (PeerNameSet, PeerNameSet, error)
|
||||
return nil, nil, err
|
||||
}
|
||||
|
||||
ourVersion := peers.ourself.Version
|
||||
|
||||
// By this point, we know the update doesn't refer to any peers we
|
||||
// have no knowledge of. We can now apply the update. Start by
|
||||
// adding in any new peers.
|
||||
@@ -349,13 +347,6 @@ func (peers *Peers) ApplyUpdate(update []byte) (PeerNameSet, PeerNameSet, error)
|
||||
updateNames[peer.Name] = void
|
||||
}
|
||||
|
||||
if peers.ourself.Version != ourVersion {
|
||||
// Our short id changed, i.e. due to a short ID
|
||||
// change. So we need to include ourself in the
|
||||
// update
|
||||
newUpdate[peers.ourself.Name] = void
|
||||
}
|
||||
|
||||
return updateNames, newUpdate, nil
|
||||
}
|
||||
|
||||
|
||||
@@ -69,3 +69,17 @@
|
||||
s.parentNode.insertBefore(wf, s);
|
||||
})();
|
||||
</script>
|
||||
<script type="text/javascript">
|
||||
piAId = '124932';
|
||||
piCId = '85570';
|
||||
|
||||
(function() {
|
||||
function async_load(){
|
||||
var s = document.createElement('script'); s.type = 'text/javascript';
|
||||
s.src = ('https:' == document.location.protocol ? 'https://pi' : 'http://cdn') + '.pardot.com/pd.js';
|
||||
var c = document.getElementsByTagName('script')[0]; c.parentNode.insertBefore(s, c);
|
||||
}
|
||||
if(window.attachEvent) { window.attachEvent('onload', async_load); }
|
||||
else { window.addEventListener('load', async_load, false); }
|
||||
})();
|
||||
</script>
|
||||
+4
-4
@@ -57,13 +57,13 @@ All docker commands can be run via the proxy, so it is safe to adjust
|
||||
your `DOCKER_HOST` to point at the proxy. Weave provides a convenient
|
||||
command for this:
|
||||
|
||||
host1$ eval "$(weave env)"
|
||||
host1$ eval $(weave env)
|
||||
host1$ docker ps
|
||||
...
|
||||
|
||||
The prior settings can be restored with
|
||||
|
||||
host1$ eval "$(weave env --restore)"
|
||||
host1$ eval $(weave env --restore)
|
||||
|
||||
Alternatively, the proxy host can be set on a per-command basis with
|
||||
|
||||
@@ -194,7 +194,7 @@ ultimately be handed over to weaveDNS for registration.
|
||||
For instance, we can launch the proxy using all three flags
|
||||
|
||||
host1$ weave launch-router && weave launch-proxy --hostname-from-label hostname-label --hostname-match '^aws-[0-9]+-(.*)$' --hostname-replacement 'my-app-$1'
|
||||
host1$ eval "$(weave env)"
|
||||
host1$ eval $(weave env)
|
||||
|
||||
Note how regexp substitution groups should be prepended with a dollar sign
|
||||
(e.g. `$1`). For further details on the regular expression syntax please see
|
||||
@@ -264,7 +264,7 @@ with
|
||||
|
||||
$ mkdir -pv ~/.docker
|
||||
$ cp -v {ca,cert,key}.pem ~/.docker
|
||||
$ eval "$(weave env)"
|
||||
$ eval $(weave env)
|
||||
$ export DOCKER_TLS_VERIFY=1
|
||||
$ docker version
|
||||
...
|
||||
|
||||
Reference in new issue
Block a user