Merge pull request #651 from weaveworks/move-weavedns-docs
Update docs index: move WeaveDNS docs and add Getting Started Guides
This commit is contained in:
commit
d106c56c00
4 files changed
+14
-5
No files matched your search
@@ -136,7 +136,7 @@ to each other.
|
||||
* [Troubleshooting](http://docs.weave.works/weave/latest_release/troubleshooting.html)
|
||||
* [Building](http://docs.weave.works/weave/latest_release/building.html)
|
||||
* [How it works](http://docs.weave.works/weave/latest_release/how-it-works.html)
|
||||
* [Automatic Discovery with WeaveDNS](https://github.com/weaveworks/weave/tree/latest_release/weavedns#readme)
|
||||
* [Automatic Discovery with WeaveDNS](http://docs.weave.works/weave/latest_release/weavedns-readme.html)
|
||||
|
||||
## Contact Us
|
||||
|
||||
|
||||
+3
-4
@@ -5,12 +5,11 @@ layout: default
|
||||
|
||||
# weave documentation
|
||||
|
||||
* [Introduction and example (in README)](https://github.com/weaveworks/weave#readme)
|
||||
* [Introduction, Installation and Example](https://github.com/weaveworks/weave#readme)
|
||||
* [Getting Started Guides](http://weave.works/guides/)
|
||||
* [Features](features.html)
|
||||
* [Automatic Discovery with WeaveDNS](weavedns-readme.html)
|
||||
* [Troubleshooting](troubleshooting.html)
|
||||
* [Building](building.html)
|
||||
* [How it works](how-it-works.html)
|
||||
* [Contact information](https://github.com/weaveworks/weave#contact-us)
|
||||
* *Installation Notes*
|
||||
* [Using with boot2docker](boot2docker.html)
|
||||
* [Using with systemd](systemd.html)
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
title: WeaveDNS Design Notes
|
||||
layout: default
|
||||
---
|
||||
|
||||
# Weave DNS (service discovery) design
|
||||
|
||||
The model is that each host has a service that is notified of
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
title: Automatic Discovery with WeaveDNS
|
||||
layout: default
|
||||
---
|
||||
|
||||
# Weave DNS server
|
||||
|
||||
The Weave DNS server answers name queries in a Weave network. This
|
||||
Reference in new issue
Block a user