* 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>
* DTR release notes for March 2020 Amberjack patch release
* updating dtr and ucp product versions and links to tarballs
* fixing typo
Co-authored-by: Dawn W Docker <dawn.wood@users.noreply.github.com>
* fixing Hub and DTR broken links
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Fixing another link
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
This change is proposed because DTR backup will fail in the same way as an installation if Administrators are unable to deploy on "UCP manager nodes or nodes running DTR". Tracked by FIELD-1939.
* 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>
Changed the order for the actions to be in chronological order. Currently, it seems you have to find the replica ID before running the command. This is emphasized by the "Then run". This is not the case. You use the replica ID after you run the command.
* Added info about load balancer to Step 3: Install
DTR; various formatting changes to the page.
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* formatting
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
Because in the preceding paragraphs we talk about creating a bucket and/or a user and there are also bucket and user policies, I thing it is important to make clear the example policy is a 'user' policy and not a bucket policy.
Added a link to AWS for information about creating a user policy.
Sebastiaan van Stijn