Merge pull request #1759 from SvenDowideit/fix-new-doc-metadata

Add topics to the menu
pull/1762/head
Sven Dowideit 2016-06-01 10:35:14 -07:00
commit e66f9c1440
5 changed files with 16 additions and 3 deletions

View File

@ -1,8 +1,11 @@
<!--[metadata]>
+++
title = "registry Compatibility"
title = "Compatibility"
description = "describes get by digest pitfall"
keywords = ["registry, manifest, images, tags, repository, distribution, digest"]
[menu.main]
parent="smn_registry_ref"
weight=9
+++
<![end-metadata]-->
@ -78,4 +81,4 @@ constraints of CAS.*
For this reason if a manifest is pulled by _digest_ from a registry 2.3 with Docker
Engine 1.9 and older, and the manifest was pushed with Docker Engine 1.10, a
security check will cause the Engine to receive a manifest it cannot use and the
pull will fail.
pull will fail.

View File

@ -1,8 +1,11 @@
<!--[metadata]>
+++
title = "registry deprecation"
title = "Deprecated Features"
description = "describes deprecated functionality"
keywords = ["registry, manifest, images, signatures, repository, distribution, digest"]
[menu.main]
parent="smn_registry_ref"
weight=8
+++
<![end-metadata]-->

View File

@ -3,6 +3,9 @@
title = "Garbage Collection"
description = "High level discussion of garbage collection"
keywords = ["registry, garbage, images, tags, repository, distribution"]
[menu.main]
parent="smn_registry_ref"
weight=4
+++
<![end-metadata]-->

View File

@ -6,6 +6,7 @@ keywords = ["registry, on-prem, images, tags, repository, distribution"]
aliases = ["/registry/overview/"]
[menu.main]
parent="smn_registry"
weight=1
+++
<![end-metadata]-->

View File

@ -3,6 +3,9 @@
title = "Testing an insecure registry"
description = "Deploying a Registry in an insecure fashion"
keywords = ["registry, on-prem, images, tags, repository, distribution, insecure"]
[menu.main]
parent="smn_registry_ref"
weight=5
+++
<![end-metadata]-->