* Fix incorrect links in compose section
there's a bug causing wrapped links to not work, and replacing
some links to point to the .md file, so that IDE's can check
if the anchors are valid. Also replaced some links to point
to their new location.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* engine/swarm: update links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix various broken links
There's a bug in the "jekyll-relative-links" plugin that causes wrapped links to not work.
Also replacing some links to point to the .md file, so that IDE's can check if the anchors
are valid. Finally, replaced some links to point to their new locations, so that users don't
get redirected..
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fixed links to previous versions
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Fixed another link
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
Replace all occurrences of
```foo
{% raw %}
bar
{% endraw %}
```
(which generates spurious empty lines in the rendered pre block) with
{% raw %}
```foo
bar
```
{% endraw %}
Also, fix some occurrences where the raw section is too large and
prevented interpretation of Jekyll directives.
This is the syntax used in the documentation of Jekyll itself:
https://raw.githubusercontent.com/jekyll/jekyll/master/docs/_docs/templates.md
FTR, done with two perl substitutions:
'^([\t ]*```[^\n]*
)([ \t]*\{% raw %\}[^\n]*
)' '$2$1'
and
'^([ \t]*\{% endraw %\}[^\n]*
)([\t ]*```[^\n]*
)' '$2$1'
and manually tweaks. A mechanical check would be most useful.
Signed-off-by: Akim Demaille <akim.demaille@docker.com>
Commands were failing because the DTR version number wasn't rendering. I fixed it on this page by replacing "dtr_version" with "page.dtr_version" in three places.
* dtr-rethinkdb now houses the rethinkcli which means we no longer need
to pull the rethinkcli container from hub.
Signed-off-by: Kyle Squizzato <kyle.squizzato@docker.com>
`-z` option for tar is used to filter through gzip. This should be excluded for the restore as it was not used during the backup.
The path is also fixed as it recreated the entire path within the volumes folder.
I think the actual documentation can be confusing.
In fact if we want to completely remove a DTR cluster, we can use the destroy command, it is fine.
But, if we just want to remove a replica from a cluster, it is better to use the remove command which is safer and cleaner.
The destroy command do not send a notification to the RethinkDB on the others replicas which can be dangerous and leads to unhealthy DTR clusters.
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
This request is based on an internal support case with Genesys ( A Docker Enterprise Customer ) who confirmed through our sales department ( who has relayed they've confirmed via engineering ) that we current support installing DTR on the same nodes as UCP manager nodes. Our documentation however says this is a requirement and Genesys has requested we update our documentation to reflect this which is the basis of this change. [https://docker.my.salesforce.com/5000f00001FBE2l](Docker Support Case 00033149)
Sebastiaan van Stijn