Convert Markdown frontmatter to YAML

Some frontmatter such as the weights, menu stuff, etc is no longer used
'draft=true' becomes 'published: false'

Signed-off-by: Misty Stanley-Jones <misty@docker.com>
Upstream-commit: b30609446d212624e3d4ce814c70130b75c552a0
Component: engine
This commit is contained in:
Misty Stanley-Jones
2016-10-14 15:30:36 -07:00
parent da2b0bc963
commit 9fe833df60
119 changed files with 660 additions and 1161 deletions

View File

@ -1,17 +1,12 @@
<!--[metadata]>
+++
aliases = [
---
aliases: [
"/engine/extend/"
]
title = "Managed plugin system"
description = "How develop and use a plugin with the managed plugin system"
keywords = ["API, Usage, plugins, documentation, developer"]
advisory = "experimental"
[menu.main]
parent = "engine_extend"
weight=1
+++
<![end-metadata]-->
title: "Managed plugin system"
description: "How develop and use a plugin with the managed plugin system"
keywords: ["API, Usage, plugins, documentation, developer"]
advisory: "experimental"
---
# Docker Engine managed plugin system

View File

@ -1,14 +1,9 @@
<!--[metadata]>
+++
aliases = "/engine/extend/plugins/"
title = "Use Docker Engine plugins"
description = "How to add additional functionality to Docker with plugins extensions"
keywords = ["Examples, Usage, plugins, docker, documentation, user guide"]
[menu.main]
parent = "engine_extend"
weight=3
+++
<![end-metadata]-->
---
aliases: "/engine/extend/plugins/"
title: "Use Docker Engine plugins"
description: "How to add additional functionality to Docker with plugins extensions"
keywords: ["Examples, Usage, plugins, docker, documentation, user guide"]
---
# Use Docker Engine plugins

View File

@ -1,17 +1,12 @@
<!--[metadata]>
+++
aliases = [
---
aliases: [
"/engine/extend/"
]
title = "Plugin manifest"
description = "How develop and use a plugin with the managed plugin system"
keywords = ["API, Usage, plugins, documentation, developer"]
advisory = "experimental"
[menu.main]
parent = "engine_extend"
weight=1
+++
<![end-metadata]-->
title: "Plugin manifest"
description: "How develop and use a plugin with the managed plugin system"
keywords: ["API, Usage, plugins, documentation, developer"]
advisory: "experimental"
---
# Plugin Manifest Version 0 of Plugin V2
@ -47,7 +42,7 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`interface`** *PluginInterface*
interface implemented by the plugins, struct consisting of the following fields
- **`types`** *string array*
types indicate what interface(s) the plugin currently implements.
@ -55,9 +50,9 @@ Manifest provides the base accessible fields for working with V0 plugin format
currently supported:
- **docker.volumedriver/1.0**
- **`socket`** *string*
socket is the name of the socket the engine should use to communicate with the plugins.
the socket will be created in `/run/docker/plugins`.
@ -73,7 +68,7 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`network`** *PluginNetwork*
network of the plugin, struct consisting of the following fields
- **`type`** *string*
network type.
@ -83,11 +78,11 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **bridge**
- **host**
- **none**
- **`capabilities`** *array*
capabilities of the plugin (*Linux only*), see list [`here`](https://github.com/opencontainers/runc/blob/master/libcontainer/SPEC.md#security)
- **`mounts`** *PluginMount array*
mount of the plugin, struct consisting of the following fields, see [`MOUNTS`](https://github.com/opencontainers/runtime-spec/blob/master/config.md#mounts)
@ -95,27 +90,27 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`name`** *string*
name of the mount.
- **`description`** *string*
description of the mount.
- **`source`** *string*
source of the mount.
- **`destination`** *string*
destination of the mount.
- **`type`** *string*
mount type.
- **`options`** *string array*
options of the mount.
- **`devices`** *PluginDevice array*
device of the plugin, (*Linux only*), struct consisting of the following fields, see [`DEVICES`](https://github.com/opencontainers/runtime-spec/blob/master/config-linux.md#devices)
@ -123,11 +118,11 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`name`** *string*
name of the device.
- **`description`** *string*
description of the device.
- **`path`** *string*
path of the device.
@ -139,15 +134,15 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`name`** *string*
name of the env.
- **`description`** *string*
description of the env.
- **`value`** *string*
value of the env.
- **`args`** *PluginArgs*
args of the plugin, struct consisting of the following fields
@ -155,16 +150,16 @@ Manifest provides the base accessible fields for working with V0 plugin format
- **`name`** *string*
name of the env.
- **`description`** *string*
description of the env.
- **`value`** *string array*
values of the args.
## Example Manifest
*Example showing the 'tiborvass/no-remove' plugin manifest.*

View File

@ -1,15 +1,10 @@
<!--[metadata]>
+++
title = "Implement plugins"
description = "Develop plugins and use existing plugins for Docker Engine"
keywords = ["extend, plugins, docker, documentation, developer"]
type="menu"
[menu.main]
identifier = "engine_extend"
parent="engine_use"
weight = 0
+++
<![end-metadata]-->
---
title: "Implement plugins"
description: "Develop plugins and use existing plugins for Docker Engine"
keywords: ["extend, plugins, docker, documentation, developer"]
type: "menu"
identifier: "engine_extend"
---
<!--menu page not rendered-->

View File

@ -1,13 +1,8 @@
<!--[metadata]>
+++
title = "Plugins API"
description = "How to write Docker plugins extensions "
keywords = ["API, Usage, plugins, documentation, developer"]
[menu.main]
parent = "engine_extend"
weight=7
+++
<![end-metadata]-->
---
title: "Plugins API"
description: "How to write Docker plugins extensions "
keywords: ["API, Usage, plugins, documentation, developer"]
---
# Docker Plugin API

View File

@ -1,14 +1,9 @@
<!--[metadata]>
+++
title = "Access authorization plugin"
description = "How to create authorization plugins to manage access control to your Docker daemon."
keywords = ["security, authorization, authentication, docker, documentation, plugin, extend"]
aliases = ["/engine/extend/authorization/"]
[menu.main]
parent = "engine_extend"
weight = 4
+++
<![end-metadata]-->
---
title: "Access authorization plugin"
description: "How to create authorization plugins to manage access control to your Docker daemon."
keywords: ["security, authorization, authentication, docker, documentation, plugin, extend"]
aliases: ["/engine/extend/authorization/"]
---
# Create an authorization plugin

View File

@ -1,13 +1,8 @@
<!--[metadata]>
+++
title = "Docker network driver plugins"
description = "Network driver plugins."
keywords = ["Examples, Usage, plugins, docker, documentation, user guide"]
[menu.main]
parent = "engine_extend"
weight=5
+++
<![end-metadata]-->
---
title: "Docker network driver plugins"
description: "Network driver plugins."
keywords: ["Examples, Usage, plugins, docker, documentation, user guide"]
---
# Engine network driver plugins

View File

@ -1,13 +1,8 @@
<!--[metadata]>
+++
title = "Volume plugins"
description = "How to manage data with external volume plugins"
keywords = ["Examples, Usage, volume, docker, data, volumes, plugin, api"]
[menu.main]
parent = "engine_extend"
weight=6
+++
<![end-metadata]-->
---
title: "Volume plugins"
description: "How to manage data with external volume plugins"
keywords: ["Examples, Usage, volume, docker, data, volumes, plugin, api"]
---
# Write a volume plugin