docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #488 from gdevillele/PR_keywords_type_fix_for_dockercloud 

fix type of keywords entry in frontmatter (in /docker-cloud/ dir)
This commit is contained in:
LRubin 2016-11-09 10:25:50 -08:00 committed by GitHub
parent 8eb69ea720 bcec1ddcb2
commit 844471f473
62 changed files with 175 additions and 237 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docker-cloud/apps/api-roles.md
View File

@ -1,9 +1,8 @@
---
description: API Roles
keywords: API, Services, roles
redirect_from:
- /docker-cloud/feature-reference/api-roles/
description: API Roles
keywords:
- API, Services, roles
title: Service API roles
---
@ -32,4 +31,4 @@ $ curl -H "Authorization: $DOCKERCLOUD_AUTH" -H "Accept: application/json" $WEB_
For example, you can use information retrieved using the API to read the linked
endpoints, and use them to reconfigure a proxy container.
See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.
See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.

7
docker-cloud/apps/auto-destroy.md
View File

@ -1,9 +1,8 @@
---
description: Autodestroy
keywords: Autodestroy, service, terminate, container
redirect_from:
- /docker-cloud/feature-reference/auto-destroy/
description: Autodestroy
keywords:
- Autodestroy, service, terminate, container
title: Destroy containers automatically
---
@ -75,4 +74,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
#### Enabling autodestroy using the CLI
```
$ docker-cloud service set --autodestroy ALWAYS (name or uuid)
```
```

7
docker-cloud/apps/auto-redeploy.md
View File

@ -1,9 +1,8 @@
---
description: Autoredeploy
keywords: Autoredeploy, image, store, service
redirect_from:
- /docker-cloud/feature-reference/auto-redeploy/
description: Autoredeploy
keywords:
- Autoredeploy, image, store, service
title: Redeploy services automatically
---
@ -76,4 +75,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
{
"autoredeploy": true
}
```
```

7
docker-cloud/apps/autorestart.md
View File

@ -1,9 +1,8 @@
---
description: Automatically restart a container in Docker Cloud
keywords: container, restart, automated
redirect_from:
- /docker-cloud/feature-reference/autorestart/
description: Automatically restart a container in Docker Cloud
keywords:
- container, restart, automated
title: Restart a container automatically
---
@ -86,4 +85,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
$ docker-cloud service set --autorestart ALWAYS (name or uuid)
```
See the [API documentation](/apidocs/docker-cloud.md) for more information.
See the [API documentation](/apidocs/docker-cloud.md) for more information.

7
docker-cloud/apps/deploy-tags.md
View File

@ -1,9 +1,8 @@
---
description: Deployment tags
keywords: Deployment, tags, services
redirect_from:
- /docker-cloud/feature-reference/deploy-tags/
description: Deployment tags
keywords:
- Deployment, tags, services
title: Deployment tags
---
@ -116,4 +115,4 @@ be deployed to the nodes that match the new tags.
## Using deployment tags in the API and CLI
See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.
See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.

7
docker-cloud/apps/deploy-to-cloud-btn.md
View File

@ -1,10 +1,9 @@
---
description: Deploy to Docker Cloud
keywords: deploy, docker, cloud
redirect_from:
- /docker-cloud/feature-reference/deploy-to-cloud/
- /docker-cloud/tutorials/deploy-to-cloud/
description: Deploy to Docker Cloud
keywords:
- deploy, docker, cloud
title: Add a "Deploy to Docker Cloud" button
---
@ -61,4 +60,4 @@ where `<repo_url>` is the path to your GitHub repository. For example:
You can use your own image for the link (or no image). Our **Deploy to Docker Cloud** image is available at the following URL:
* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`
* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`

5
docker-cloud/apps/index.md
View File

@ -1,7 +1,6 @@
---
description: Manage your Docker Cloud Applications
keywords:
- applications, reference, Cloud
keywords: applications, reference, Cloud
title: Applications in Docker Cloud
---
@ -33,4 +32,4 @@ Use the following features to automate specific actions on your Docker Cloud app
* [Automatic container destroy](auto-destroy.md)
* [Automatic container restart](autorestart.md)
* [Autoredeploy](auto-redeploy.md)
* [Use triggers](triggers.md)
* [Use triggers](triggers.md)

7
docker-cloud/apps/load-balance-hello-world.md
View File

@ -1,10 +1,9 @@
---
description: Create a proxy or load balancer
keywords: proxy, load, balancer
redirect_from:
- /docker-cloud/getting-started/intermediate/load-balance-hello-world/
- /docker-cloud/tutorials/load-balance-hello-world/
description: Create a proxy or load balancer
keywords:
- proxy, load, balancer
title: Create a proxy or load balancer
---
@ -197,4 +196,4 @@ links](service-links.md).
You can try this by pointing your web browser to
*servicename.username.svc.dockerapp.io* or using *dig* or *nslookup* to see how
the service endpoint resolves.
the service endpoint resolves.

7
docker-cloud/apps/ports.md
View File

@ -1,9 +1,8 @@
---
description: Publish and expose service or container ports
keywords: publish, expose, ports, containers, services
redirect_from:
- /docker-cloud/feature-reference/ports/
description: Publish and expose service or container ports
keywords:
- publish, expose, ports, containers, services
title: Publish and expose service or container ports
---
@ -122,4 +121,4 @@ not dynamic) is assigned a DNS endpoint in the format
running, in a [round-robin
fashion](https://en.wikipedia.org/wiki/Round-robin_DNS).
You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.
You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.

7
docker-cloud/apps/service-links.md
View File

@ -1,9 +1,8 @@
---
description: Service discovery
keywords: service, discover, links
redirect_from:
- /docker-cloud/feature-reference/service-links/
description: Service discovery
keywords:
- service, discover, links
title: Service discovery and links
---
@ -162,4 +161,4 @@ Where:
These environment variables are also copied to linked containers with the `NAME_ENV_` prefix.
If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.
If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.

7
docker-cloud/apps/service-redeploy.md
View File

@ -1,9 +1,8 @@
---
description: Redeploy running services
keywords: redeploy, running, services
redirect_from:
- /docker-cloud/feature-reference/service-redeploy/
description: Redeploy running services
keywords:
- redeploy, running, services
title: Redeploy a running service
---
@ -73,4 +72,4 @@ whenever a new image is pushed. See the [Autoredeploy documentation](auto-redepl
## Redeploy a service using webhooks
You can also use **triggers** to redeploy a service, for example when its image
is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.
is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.

7
docker-cloud/apps/service-scaling.md
View File

@ -1,9 +1,8 @@
---
description: Scale your service, spawn new containers
keywords: spawn, container, service, deploy
redirect_from:
- /docker-cloud/feature-reference/service-scaling/
description: Scale your service, spawn new containers
keywords:
- spawn, container, service, deploy
title: Scale your service
---
@ -155,4 +154,4 @@ application through the CLI: 
```bash
$ docker-cloud service run --sequential [...] 
```
```

7
docker-cloud/apps/stack-yaml-reference.md
View File

@ -1,9 +1,8 @@
---
description: Stack YAML reference
keywords: YAML, stack, reference
redirect_from:
- /docker-cloud/feature-reference/stack-yaml-reference/
description: Stack YAML reference
keywords:
- YAML, stack, reference
title: Stack file YAML reference
---
@ -321,4 +320,4 @@ Stack files (`docker-cloud.yml`) were designed with `docker-compose.yml` in mind
build
external_links
env_file
```
```

7
docker-cloud/apps/stacks.md
View File

@ -1,9 +1,8 @@
---
description: Manage service stacks
keywords: service, stack, yaml
redirect_from:
- /docker-cloud/feature-reference/stacks/
description: Manage service stacks
keywords:
- service, stack, yaml
title: Manage service stacks
---
@ -126,4 +125,4 @@ You can update a stack from a YAML file by executing:
docker-cloud stack update -f docker-cloud.yml (uuid or name)
```
Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.
Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.

7
docker-cloud/apps/triggers.md
View File

@ -1,9 +1,8 @@
---
description: Use triggers
keywords: API, triggers, endpoints
redirect_from:
- /docker-cloud/feature-reference/triggers/
description: Use triggers
keywords:
- API, triggers, endpoints
title: Use triggers
---
@ -56,4 +55,4 @@ Once the trigger is revoked, it stops accepting requests.
## Using triggers in the API and CLI
See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.
See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.

7
docker-cloud/apps/volumes.md
View File

@ -1,10 +1,9 @@
---
description: Work with data volumes
keywords: data, volumes, create, reuse
redirect_from:
- /docker-cloud/tutorials/download-volume-data/
- /docker-cloud/feature-reference/volumes/
description: Work with data volumes
keywords:
- data, volumes, create, reuse
title: Work with data volumes
---
@ -67,4 +66,4 @@ You might find it helpful to download or back up the data from volumes that are
```
$ scp -r -P 2222 root@downloader-1.uuid.cont.dockerapp.io:/var/lib/mysql .
```
```

5
docker-cloud/builds/advanced.md
View File

@ -1,7 +1,6 @@
---
description: Automated builds
keywords:
- automated, build, images
keywords: automated, build, images
title: Advanced options for Autobuild and Autotest
---
@ -111,4 +110,4 @@ If you needed to give the resulting image multiple tags, or push the same image
```none
docker tag $IMAGE_NAME $DOCKER_REPO:$SOURCE_COMMIT
docker push $DOCKER_REPO:$SOURCE_COMMIT
```
```

7
docker-cloud/builds/automated-build.md
View File

@ -1,9 +1,8 @@
---
description: Automated builds
keywords: automated, build, images
redirect_from:
- /docker-cloud/feature-reference/automated-build/
description: Automated builds
keywords:
- automated, build, images
title: Automated builds
---
@ -356,4 +355,4 @@ Docker Cloud's [Autotest](automated-testing.md) feature which
integrates seamlessly with autobuild and autoredeploy.
> **Note**: While the Autotest feature builds an image for testing purposes, it
does not push the resulting image to Docker Cloud or the external registry.
does not push the resulting image to Docker Cloud or the external registry.

7
docker-cloud/builds/automated-testing.md
View File

@ -1,9 +1,8 @@
---
description: Automated tests
keywords: Automated, testing, repository
redirect_from:
- /docker-cloud/feature-reference/automated-testing/
description: Automated tests
keywords:
- Automated, testing, repository
title: Automated repository tests
---
@ -92,4 +91,4 @@ From the repository's details page, click **Timeline**.
From this tab you can see any pending, in-progress, successful, and failed
builds and test runs for the repository.
You can click any timeline entry to view the logs for each test run.
You can click any timeline entry to view the logs for each test run.

7
docker-cloud/builds/image-scan.md
View File

@ -1,7 +1,6 @@
---
description: "Docker Security Scanning: automatic image scanning"
keywords:
- Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation, trusted, builds, trusted builds, automated builds
description: 'Docker Security Scanning: automatic image scanning'
keywords: Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation, trusted, builds, trusted builds, automated builds
title: Docker Security Scanning
---
@ -181,4 +180,4 @@ components.
## Related information
* [Learn about CVE and how it compiles data](https://cve.mitre.org/about/index.html).
* [How to create a Docker Official image](/docker-hub/official_repos/)
* [How to create a Docker Official image](/docker-hub/official_repos/)

5
docker-cloud/builds/index.md
View File

@ -1,7 +1,6 @@
---
description: Manage Builds and Images in Docker Cloud
keywords:
- builds, images, Cloud
keywords: builds, images, Cloud
notoc: true
title: Builds and images overview
---
@ -24,4 +23,4 @@ running services when a build passes its tests.
* [Automated repository tests](automated-testing.md)
* [Advanced options for Autobuild and Autotest](advanced.md)
![a Docker Cloud repository's General view](images/repo-general.png)
![a Docker Cloud repository's General view](images/repo-general.png)

7
docker-cloud/builds/link-source.md
View File

@ -1,9 +1,8 @@
---
description: Link to your source code repository
keywords: sourcecode, github, bitbucket, Cloud
redirect_from:
- /docker-cloud/tutorials/link-source/
description: Link to your source code repository
keywords:
- sourcecode, github, bitbucket, Cloud
title: Link Docker Cloud to a source code provider
---
@ -152,4 +151,4 @@ unlink it both from Docker Cloud, *and* from your Bitbucket account.
> **Note**: Each repository that is configured as an automated build source
contains a webhook that notifies Docker Cloud of changes in the repository. This
webhook is not automatically removed when you revoke access to a source code
provider.
provider.

7
docker-cloud/builds/push-images.md
View File

@ -1,10 +1,9 @@
---
description: Push images to Docker Cloud
keywords: images, private, registry
redirect_from:
- /docker-cloud/getting-started/intermediate/pushing-images-to-dockercloud/
- /docker-cloud/tutorials/pushing-images-to-dockercloud/
description: Push images to Docker Cloud
keywords:
- images, private, registry
title: Push images to Docker Cloud
---
@ -56,4 +55,4 @@ Follow the <a href="http://docs.docker.com/installation/" target="_blank">offic
> Cloud, you might need to select the organization name or your username from
> the dropdown menu see other repositories.
![](images/private_image.png)
![](images/private_image.png)

5
docker-cloud/builds/repos.md
View File

@ -1,7 +1,6 @@
---
description: Create and edit Docker Cloud repositories
keywords:
- Docker Cloud repositories, automated, build, images
keywords: Docker Cloud repositories, automated, build, images
title: Docker Cloud repositories
---
@ -88,4 +87,4 @@ You can link to repositories hosted on a third party registry. This allows you t
## What's next?
Once you create or link to a repository in Docker Cloud, you can set up [automated testing](automated-testing.md) and [automated builds](automated-build.md).
Once you create or link to a repository in Docker Cloud, you can set up [automated testing](automated-testing.md) and [automated builds](automated-build.md).

7
docker-cloud/docker-errors-faq.md
View File

@ -1,9 +1,8 @@
---
description: Known Docker Engine issues in Docker Cloud
keywords: Engine, issues, troubleshoot
redirect_from:
- /docker-cloud/faq/docker-errors-faq/
description: Known Docker Engine issues in Docker Cloud
keywords:
- Engine, issues, troubleshoot
title: Known issues in Docker Cloud
---
@ -102,4 +101,4 @@ Timeouts occur when pulling the image takes more than 10 minutes. This can somet
#### Workaround
Restart the `dockercloud-agent` service (`sudo service dockercloud-agent restart`) on the node, or restart the node.
Restart the `dockercloud-agent` service (`sudo service dockercloud-agent restart`) on the node, or restart the node.

5
docker-cloud/dockerid.md
View File

@ -1,7 +1,6 @@
---
description: Using your DockerID to log in to Docker Cloud
keywords:
- one, two, three
keywords: one, two, three
title: Docker ID and Docker Cloud settings
---
@ -53,4 +52,4 @@ Like free Docker Hub accounts, free Docker Cloud accounts come with one free
private repository.
If you require more private repositories, visit your **Cloud settings** and
select **Plan** to see the available paid accounts.
select **Plan** to see the available paid accounts.

7
docker-cloud/getting-started/connect-infra.md
View File

@ -1,9 +1,8 @@
---
description: How to link Docker Cloud to a hosted cloud services provider or your own hosts
keywords: node, create, understand
redirect_from:
- /docker-cloud/getting-started/use-hosted/
description: How to link Docker Cloud to a hosted cloud services provider or your own hosts
keywords:
- node, create, understand
title: Link to your infrastructure
---
@ -29,4 +28,4 @@ Then, use the one of the detailed tutorials below to link your account. You shou
If you are not using a cloud services provider and are using your own hosts, you'll need to install the Docker Cloud Agent on those hosts so that Docker Cloud can communicate with them. Follow the directions at [Bring Your Own Node instructions](../infrastructure/byoh.md). Open these instructions in a new window or tab so you can return to this tutorial once you're done linking your hosts.
## Ready to go?
Once you've linked to your cloud services provider or to your own hosts, [continue the tutorial and deploy your first node](your_first_node.md).
Once you've linked to your cloud services provider or to your own hosts, [continue the tutorial and deploy your first node](your_first_node.md).

7
docker-cloud/getting-started/deploy-app/10_provision_a_data_backend_for_your_service.md
View File

@ -1,10 +1,9 @@
---
description: Provision a data backend for the service
keywords: provision, Python, service
redirect_from:
- /docker-cloud/getting-started/python/10_provision_a_data_backend_for_your_service/
- /docker-cloud/getting-started/golang/10_provision_a_data_backend_for_your_service/
description: Provision a data backend for the service
keywords:
- provision, Python, service
title: Provision a data backend for your service
---
@ -64,4 +63,4 @@ $ curl lb-1.$DOCKER_ID_USER.cont.dockerapp.io
Hello World</br>Hostname: web-3</br>Counter: 5%
```
Next, we'll look at [Stackfiles for your service](11_service_stacks.md)
Next, we'll look at [Stackfiles for your service](11_service_stacks.md)

7
docker-cloud/getting-started/deploy-app/11_service_stacks.md
View File

@ -1,9 +1,8 @@
---
description: Stackfiles for your service
keywords: Python, service, stack
redirect_from:
- /docker-cloud/getting-started/python/11_service_stacks/
description: Stackfiles for your service
keywords:
- Python, service, stack
title: Stackfiles for your service
---
@ -67,4 +66,4 @@ Or you can specify the YML file to use and its location:
$ docker-cloud up -f /usr/dockercloud/quickstart-python/docker-cloud.yml
```
Next, we'll do some [Data management with Volumes](12_data_management_with_volumes.md)
Next, we'll do some [Data management with Volumes](12_data_management_with_volumes.md)

7
docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md
View File

@ -1,9 +1,8 @@
---
description: Data management with Volumes
keywords: Python, data, management
redirect_from:
- /docker-cloud/getting-started/python/12_data_management_with_volumes/
description: Data management with Volumes
keywords:
- Python, data, management
title: Data management with volumes
---
@ -135,4 +134,4 @@ set up a volume to save the data.
There's lots more to learn about Docker Cloud, so check out [the rest of our documentation](/docker-cloud/), the [API and CLI Documentation](../../../apidocs/docker-cloud.md), and our [Knowledge Hub](https://success.docker.com/Cloud) and [Docker Cloud Forums](https://forums.docker.com/c/docker-cloud).
Happy Docking!
Happy Docking!

7
docker-cloud/getting-started/deploy-app/1_introduction.md
View File

@ -1,10 +1,9 @@
---
description: Deploy an app to Docker Cloud
keywords: deploy, Python, application
redirect_from:
- /docker-cloud/getting-started/python/1_introduction/
- /docker-cloud/getting-started/golang/1_introduction/
description: Deploy an app to Docker Cloud
keywords:
- deploy, Python, application
title: Introduction to deploying an app in Docker Cloud
---
@ -21,4 +20,4 @@ This tutorial assumes that you have:
Let's get started!
[Set up your environment](2_set_up.md).
[Set up your environment](2_set_up.md).

7
docker-cloud/getting-started/deploy-app/2_set_up.md
View File

@ -1,10 +1,9 @@
---
description: Set up the application
keywords: Python, application, setup
redirect_from:
- /docker-cloud/getting-started/python/2_set_up/
- /docker-cloud/getting-started/golang/2_set_up/
description: Set up the application
keywords:
- Python, application, setup
title: Set up your environment
---
@ -78,4 +77,4 @@ If you don't want to do this, make sure you substitute your username for $DOCKER
$ export DOCKER_ID_USER=my-username
```
Next up, we'll [Prepare the app](3_prepare_the_app.md).
Next up, we'll [Prepare the app](3_prepare_the_app.md).

7
docker-cloud/getting-started/deploy-app/3_prepare_the_app.md
View File

@ -1,10 +1,9 @@
---
description: Prepare the application
keywords: Python, prepare, application
redirect_from:
- /docker-cloud/getting-started/python/3_prepare_the_app/
- /docker-cloud/getting-started/golang/3_prepare_the_app/
description: Prepare the application
keywords:
- Python, prepare, application
title: Prepare the application
---
@ -45,4 +44,4 @@ $ docker build --tag quickstart-python .
$ docker build --tag quickstart-go .
```
Next, we [Push the Docker image to Docker Cloud's Registry](4_push_to_cloud_registry.md).
Next, we [Push the Docker image to Docker Cloud's Registry](4_push_to_cloud_registry.md).

7
docker-cloud/getting-started/deploy-app/4_push_to_cloud_registry.md
View File

@ -1,10 +1,9 @@
---
description: Push the Docker image to Docker Cloud's Registry
keywords: image, Docker, cloud
redirect_from:
- /docker-cloud/getting-started/python/4_push_to_cloud_registry/
- /docker-cloud/getting-started/golang/4_push_to_cloud_registry/
description: Push the Docker image to Docker Cloud's Registry
keywords:
- image, Docker, cloud
title: Push the image to Docker Cloud's registry
---
@ -47,4 +46,4 @@ my-username/quickstart-python
my-username/quickstart-go
```
Next: [Deploy the app as a Docker Cloud service](5_deploy_the_app_as_a_service.md).
Next: [Deploy the app as a Docker Cloud service](5_deploy_the_app_as_a_service.md).

7
docker-cloud/getting-started/deploy-app/5_deploy_the_app_as_a_service.md
View File

@ -1,10 +1,9 @@
---
description: Deploy the app as a Docker Cloud service
keywords: Python, deploy, Cloud
redirect_from:
- /docker-cloud/getting-started/python/5_deploy_the_app_as_a_service/
- /docker-cloud/getting-started/golang/5_deploy_the_app_as_a_service/
description: Deploy the app as a Docker Cloud service
keywords:
- Python, deploy, Cloud
title: Deploy the app as a Docker Cloud service
---
@ -85,4 +84,4 @@ Hello World!</br>Hostname: web-1</br>Counter: Redis Cache not found, counter dis
**CONGRATULATIONS!** You've deployed your first service using Docker Cloud.
Next: [Define environment variables](6_define_environment_variables.md).
Next: [Define environment variables](6_define_environment_variables.md).

7
docker-cloud/getting-started/deploy-app/6_define_environment_variables.md
View File

@ -1,10 +1,9 @@
---
description: Define environment variables
keywords: Python, service, environment, service
redirect_from:
- /docker-cloud/getting-started/python/6_define_environment_variables/
- /docker-cloud/getting-started/golang/6_define_environment_variables/
description: Define environment variables
keywords:
- Python, service, environment, service
title: Define environment variables
---
@ -72,4 +71,4 @@ Wondering where the default value for the **NAME** environment variable is set?
ENV NAME World
```
Next, we'll try [Scaling the service](7_scale_the_service.md).
Next, we'll try [Scaling the service](7_scale_the_service.md).

7
docker-cloud/getting-started/deploy-app/7_scale_the_service.md
View File

@ -1,10 +1,9 @@
---
description: Scale the service
keywords: scale, Python, service
redirect_from:
- /docker-cloud/getting-started/python/7_scale_the_service/
- /docker-cloud/getting-started/golang/7_scale_the_service/
description: Scale the service
keywords:
- scale, Python, service
title: Scale the service
---
@ -67,4 +66,4 @@ Hello Python Users!</br>Hostname: web-2</br>Counter: Redis Cache not found, coun
Congratulations! You now have *two* containers running in your **web** service.
Next: [View service logs](8_view_logs.md)
Next: [View service logs](8_view_logs.md)

7
docker-cloud/getting-started/deploy-app/8_view_logs.md
View File

@ -1,10 +1,9 @@
---
description: View service logs
keywords: View, logs, Python
redirect_from:
- /docker-cloud/getting-started/python/8_view_logs/
- /docker-cloud/getting-started/golang/8_view_logs/
description: View service logs
keywords:
- View, logs, Python
title: View service logs
---
@ -37,4 +36,4 @@ $ docker-cloud container logs web-1
Visit your application using curl or your browser again. Run the `service logs web` command again, and you will see another log message for your visit.
Next, let's explore how to [Load balance the service](9_load-balance_the_service.md).
Next, let's explore how to [Load balance the service](9_load-balance_the_service.md).

7
docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md
View File

@ -1,10 +1,9 @@
---
description: Load-balance the service
keywords: load, balance, Python
redirect_from:
- /docker-cloud/getting-started/python/9_load-balance_the_service/
- /docker-cloud/getting-started/golang/9_load-balance_the_service/
description: Load-balance the service
keywords:
- load, balance, Python
title: Load-balance the service
---
@ -72,4 +71,4 @@ Hello Friendly Users!</br>Hostname: web-2</br>Counter: Redis Cache not found, co
You can learn more about *dockercloud/haproxy*, our free open source HAProxy image <a href="https://github.com/docker/dockercloud-haproxy" target="_blank">here</a>.
Next: [Provision a data backend for your service](10_provision_a_data_backend_for_your_service.md)
Next: [Provision a data backend for your service](10_provision_a_data_backend_for_your_service.md)

7
docker-cloud/getting-started/deploy-app/index.md
View File

@ -1,10 +1,9 @@
---
description: Go or Python and Docker Cloud
keywords: Python, Go, Docker, Cloud, application
redirect_from:
- /docker-cloud/getting-started/python/
- /docker-cloud/getting-started/golang/
description: Go or Python and Docker Cloud
keywords:
- Python, Go, Docker, Cloud, application
title: Deploy an application
---
@ -19,4 +18,4 @@ title: Deploy an application
* [Load-balance the service](9_load-balance_the_service.md)
* [Provision a data backend for the service](10_provision_a_data_backend_for_your_service.md)
* [Stackfiles for your service](11_service_stacks.md)
* [Data management with Volumes](12_data_management_with_volumes.md)
* [Data management with Volumes](12_data_management_with_volumes.md)

5
docker-cloud/getting-started/index.md
View File

@ -1,8 +1,7 @@
---
description: 'Getting Started with Docker Cloud: Setting up a node using a hosted
cloud provider or your own nodes, deploying a service and clustering.'
keywords:
- one, two, three
keywords: one, two, three
title: Getting started with Docker Cloud
---
@ -19,4 +18,4 @@ If you're completely new to Docker Cloud, start here!
* [Deploy your first node](your_first_node.md) Then, deploy your first nodes,
* [Create your first service](your_first_service.md) ...And finish by deploying your first service.
Ready to deploy your first web service? [Deploy a web application in Docker Cloud](deploy-app/index.md)
Ready to deploy your first web service? [Deploy a web application in Docker Cloud](deploy-app/index.md)

7
docker-cloud/getting-started/intro_cloud.md
View File

@ -1,9 +1,8 @@
---
description: Introducing Docker Cloud concepts and terminology
keywords: node, create, understand
redirect_from:
- /docker-cloud/getting-started/beginner/intro_cloud/
description: Introducing Docker Cloud concepts and terminology
keywords:
- node, create, understand
title: Introducing Docker Cloud
---
@ -35,4 +34,4 @@ Services are logical groups of containers from the same image. Services make it
## Let's get started!
Log in to <a href="https://cloud.docker.com" target="_blank">Docker Cloud</a> using your Docker ID. (These are the same credentials you used for Docker Hub if you had an account there.)
Start here [by linking your infrastructure to Docker Cloud](connect-infra.md).
Start here [by linking your infrastructure to Docker Cloud](connect-infra.md).

7
docker-cloud/getting-started/your_first_node.md
View File

@ -1,10 +1,9 @@
---
description: Deploy your first node on Docker Cloud
keywords: node, create, understand
redirect_from:
- /docker-cloud/getting-started/beginner/your_first_node/
- /docker-cloud/getting-started/beginner/deploy_first_node/
description: Deploy your first node on Docker Cloud
keywords:
- node, create, understand
title: Deploy your first node
---
@ -42,4 +41,4 @@ Now that you've got at least one **node** deployed, it's time to deploy your fir
Remember that a service is a group of containers from the same container image. Services make it simple to scale your application across a number of nodes. They can also be linked one to another even if they are deployed on different nodes, regions, or even on different cloud providers.
[Continue the tutorial and deploy your first service](your_first_service.md).
[Continue the tutorial and deploy your first service](your_first_service.md).

7
docker-cloud/getting-started/your_first_service.md
View File

@ -1,10 +1,9 @@
---
description: Deploy your first service on Docker Cloud
keywords: service, Cloud, three
redirect_from:
- /docker-cloud/getting-started/beginner/your_first_service/
- /docker-cloud/getting-started/beginner/deploy_first_service/
description: Deploy your first service on Docker Cloud
keywords:
- service, Cloud, three
title: Create your first service
---
@ -119,4 +118,4 @@ Click the links icon to the right of the endpoint. This opens a new tab and show
### What's next?
Learn more about [scaling your service](../apps/service-scaling.md), or check out some of our other [Deploy an app tutorial](deploy-app/index.md).
Learn more about [scaling your service](../apps/service-scaling.md), or check out some of our other [Deploy an app tutorial](deploy-app/index.md).

5
docker-cloud/index.md
View File

@ -1,7 +1,6 @@
---
description: Docker Cloud
keywords:
- Docker, cloud
keywords: Docker, cloud
notoc: true
title: Welcome to the Docker Cloud docs!
---
@ -42,4 +41,4 @@ title: Welcome to the Docker Cloud docs!
<tr>
<td class="sherbet" colspan="2"> <a href="https://docs.docker.com/apidocs/docker-cloud/">API Docs</a> || <a href="docker-errors-faq.md">Frequently Asked Questions</a> || <a href="release-notes.md">Release Notes</a></td>
</tr>
</table>
</table>

7
docker-cloud/infrastructure/byoh.md
View File

@ -1,11 +1,10 @@
---
description: Use the Docker Cloud Agent
keywords: agent, Cloud, install
redirect_from:
- /docker-cloud/feature-reference/byoh/
- /docker-cloud/tutorials/byoh/
- /docker-cloud/getting-started/use-byon/
description: Use the Docker Cloud Agent
keywords:
- agent, Cloud, install
title: Use the Docker Cloud Agent
---
@ -128,4 +127,4 @@ script also tries to install the kernel headers required for `AUFS` support.
> **Note**: If you remove, upgrade, or install over the version of Docker Engine bundled with the Docker Cloud Agent, your nodes may not maintain a connection with Docker Cloud correctly. You will have to reinstall a compatible Engine version (currently version 1.11.2-cs5). Contact Docker Support for more information.
* If you were already using the `AUFS` storage driver before installing `dockercloud-agent`, your existing containers and images appear automatically once installation finishes.
* If you were using `devicemapper` or any other storage driver, and the `AUFS` driver installs successfully you will not be able to use your existing containers and images. You can check if the installation succeeded by running `docker info | grep Storage`.
* If you were using `devicemapper` or any other storage driver, and the `AUFS` driver installs successfully you will not be able to use your existing containers and images. You can check if the installation succeeded by running `docker info | grep Storage`.

7
docker-cloud/infrastructure/cloud-on-aws-faq.md
View File

@ -1,9 +1,8 @@
---
description: Docker Cloud on AWS
keywords: Cloud, AWS, faq
redirect_from:
- /docker-cloud/faq/cloud-on-aws-faq/
description: Docker Cloud on AWS
keywords:
- Cloud, AWS, faq
title: Use Docker Cloud on AWS
---
@ -154,4 +153,4 @@ Use the <a href="https://hub.docker.com/r/dockercloud/dockup/"
target="_blank">dockercloud/dockup</a> utility image to back up your volumes.
You only need to run it taking the volumes of the container you want to back up
with `volumes-from` and pass it the environment configuration of the container.
You can find more information in its Github repository.
You can find more information in its Github repository.

7
docker-cloud/infrastructure/cloud-on-packet.net-faq.md
View File

@ -1,9 +1,8 @@
---
description: Docker Cloud and Packet.net
keywords: Packet.net, Cloud, drives
redirect_from:
- /docker-cloud/faq/cloud-on-packet.net-faq/
description: Docker Cloud and Packet.net
keywords:
- Packet.net, Cloud, drives
title: Use Docker Cloud and Packet.net
---
@ -54,4 +53,4 @@ Packet.net copies SSH keys into the created device. This means you can upload yo
Here is a list of known errors thrown by Packet.net API:
- **You have reached the maximum number of projects you can create (number)**. Please contact `help@packet.net` -> Packet.net limits the number of projects that an account can create. Delete projects in the account or contact [Packet.net](https://www.packet.net/) support to increase the limit.
- **There is an error with your Packet.net account**. Please contact `help@packet.net` -> There is something else wrong with your Packet.net account. Contact [Packet.net](https://www.packet.net/) for more details.
- **There is an error with your Packet.net account**. Please contact `help@packet.net` -> There is something else wrong with your Packet.net account. Contact [Packet.net](https://www.packet.net/) for more details.

7
docker-cloud/infrastructure/deployment-strategies.md
View File

@ -1,9 +1,8 @@
---
description: Schedule a deployment
keywords: schedule, deployment, container
redirect_from:
- /docker-cloud/feature-reference/deployment-strategies/
description: Schedule a deployment
keywords:
- schedule, deployment, container
title: Container distribution strategies
---
@ -52,4 +51,4 @@ When a service uses the `EVERY_NODE` strategy:
> **Note**: Because of how links are configured when using the **every node**
> strategy, you cannot currently switch from **every node** to **high
> availability** or **emptiest node** and vice versa.
> availability** or **emptiest node** and vice versa.

7
docker-cloud/infrastructure/docker-upgrade.md
View File

@ -1,10 +1,9 @@
---
description: Upgrade Docker Engine on a node
keywords: upgrade, engine, node
redirect_from:
- /docker-cloud/feature-reference/docker-upgrade/
- /docker-cloud/tutorials/docker-upgrade/
description: Upgrade Docker Engine on a node
keywords:
- upgrade, engine, node
title: Upgrade Docker Engine on a node
---
@ -33,4 +32,4 @@ restarted.
# Upgrading nodes using the API and CLI
See our [API and CLI documentation](/apidocs/docker-cloud.md#upgrade-docker-daemon34) for more information on how to upgrade nodes with our API, SDKs and the CLI.
See our [API and CLI documentation](/apidocs/docker-cloud.md#upgrade-docker-daemon34) for more information on how to upgrade nodes with our API, SDKs and the CLI.

5
docker-cloud/infrastructure/index.md
View File

@ -1,7 +1,6 @@
---
description: Manage network in Docker Cloud
keywords:
- nodes, hosts, infrastructure, Cloud
keywords: nodes, hosts, infrastructure, Cloud
title: Docker Cloud infrastructure overview
---
@ -71,4 +70,4 @@ The pages in this section explain how to link Docker Cloud to your infrastructur
* [Link to Microsoft Azure hosts](link-azure.md)
* [Link to Packet hosts](link-packet.md)
* [Using Docker Cloud and Packet FAQ](cloud-on-packet.net-faq.md)
* [Link to SoftLayer hosts](link-softlayer.md)
* [Link to SoftLayer hosts](link-softlayer.md)

7
docker-cloud/infrastructure/link-aws.md
View File

@ -1,10 +1,9 @@
---
description: Link your Amazon Web Services account
keywords: AWS, Cloud, link
redirect_from:
- /docker-cloud/getting-started/beginner/link-aws/
- /docker-cloud/getting-started/link-aws/
description: Link your Amazon Web Services account
keywords:
- AWS, Cloud, link
title: Link an Amazon Web Services account
---
@ -123,4 +122,4 @@ Once you've created the a `dockercloud-policy`, attached it to a
## What's next?
You're ready to start using AWS as the infrastructure provider
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

7
docker-cloud/infrastructure/link-azure.md
View File

@ -1,10 +1,9 @@
---
description: Link your Microsoft Azure account
keywords: Microsoft, Azure, account
redirect_from:
- /docker-cloud/getting-started/beginner/link-azure/
- /docker-cloud/getting-started/link-azure/
description: Link your Microsoft Azure account
keywords:
- Microsoft, Azure, account
title: Link a Microsoft Azure account
---
@ -40,4 +39,4 @@ Go back to Docker Cloud and enter the subscription ID in the **Azure credentials
## What's next?
You're ready to start using Microsoft Azure as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using Microsoft Azure as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

7
docker-cloud/infrastructure/link-do.md
View File

@ -1,10 +1,9 @@
---
description: Link your DigitalOcean account
keywords: link, DigitalOcean, account
redirect_from:
- /docker-cloud/getting-started/beginner/link-do/
- /docker-cloud/getting-started/link-do/
description: Link your DigitalOcean account
keywords:
- link, DigitalOcean, account
title: Link a DigitalOcean account
---
@ -29,4 +28,4 @@ Once you log in, a message appears prompting you to confirm the link.
## What's next?
You're ready to start using using DigitalOcean as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using using DigitalOcean as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

7
docker-cloud/infrastructure/link-packet.md
View File

@ -1,10 +1,9 @@
---
description: Link your Packet account
keywords: Packet, link, Cloud
redirect_from:
- /docker-cloud/getting-started/beginner/link-packet/
- /docker-cloud/getting-started/link-packet/
description: Link your Packet account
keywords:
- Packet, link, Cloud
title: Link a Packet account
---
@ -26,4 +25,4 @@ Go back to the Docker Cloud tab and paste the new API key in the `Authentication
## What's next?
You're ready to start using Packet as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using Packet as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

7
docker-cloud/infrastructure/link-softlayer.md
View File

@ -1,10 +1,9 @@
---
description: Link your SoftLayer account
keywords: SoftLayer, link, cloud
redirect_from:
- /docker-cloud/getting-started/beginner/link-softlayer/
- /docker-cloud/getting-started/link-softlayer/
description: Link your SoftLayer account
keywords:
- SoftLayer, link, cloud
title: Link a SoftLayer account
---
@ -70,4 +69,4 @@ Copy and paste the `username` and the `API Key` you received from SoftLayer into
## What's next?
You're ready to start using SoftLayer as the infrastructure provider
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

7
docker-cloud/infrastructure/ssh-into-a-node.md
View File

@ -1,11 +1,10 @@
---
description: SSHing into a Docker Cloud-managed node
keywords: ssh, Cloud, node
redirect_from:
- /docker-cloud/getting-started/intermediate/ssh-into-a-node/
- /docker-cloud/tutorials/ssh-into-a-node/
- /docker-cloud/faq/how-ssh-nodes/
description: SSHing into a Docker Cloud-managed node
keywords:
- ssh, Cloud, node
title: SSH into a Docker Cloud-managed node
---
@ -102,4 +101,4 @@ Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-40-generic x86_64)
https://landscape.canonical.com/
Last login: Mon Feb 2 23:29:54 2015 from pool-108-30-19-181.nycmny.fios.verizon.net
root@13e9d739-admin:~#
```
```

7
docker-cloud/installing-cli.md
View File

@ -1,11 +1,10 @@
---
description: Using the Docker Cloud CLI on Linux, Windows, and macOS, installing, updating, uninstall
keywords: cloud, command-line, CLI
redirect_from:
- /docker-cloud/getting-started/intermediate/installing-cli/
- /docker-cloud/getting-started/installing-cli/
- /docker-cloud/tutorials/installing-cli/
description: Using the Docker Cloud CLI on Linux, Windows, and macOS, installing, updating, uninstall
keywords:
- cloud, command-line, CLI
title: The Docker Cloud CLI
---
@ -111,4 +110,4 @@ Open your Terminal application and execute the following command:
```
$ brew uninstall docker-cloud
```
```

5
docker-cloud/orgs.md
View File

@ -1,7 +1,6 @@
---
description: Docker Cloud for Organizations and Teams
keywords:
- organizations, teams, Docker Cloud, resources, permissions
keywords: organizations, teams, Docker Cloud, resources, permissions
title: Organizations and Teams in Docker Cloud
---
@ -226,4 +225,4 @@ keys.
To create resources for an Organization, log in to Docker Cloud and switch to the
Organization account. Create the repositories, services, stacks, or node
clusters as you would for any other account.
clusters as you would for any other account.

5
docker-cloud/overview.md
View File

@ -1,7 +1,6 @@
---
description: Docker Cloud Overview
keywords:
- Docker, cloud, three
keywords: Docker, cloud, three
title: Docker Cloud overview
---
@ -42,4 +41,4 @@ image, you can use it to produce containers, which make up a service, or use
Docker Cloud's stackfiles to combine it with other services and microservices,
to form a full application.
![](images/cloud-stack.png)
![](images/cloud-stack.png)

5
docker-cloud/release-notes.md
View File

@ -1,7 +1,6 @@
---
description: Docker Cloud
keywords:
- Docker, cloud, release, notes
keywords: Docker, cloud, release, notes
title: Docker Cloud release notes
---
@ -78,4 +77,4 @@ The following release notes document changes since [Tutum v0.19.5](https://suppo
### Known issues
- **Documentation screen captures** in most cases still reflect the Tutum interface and branding. We will update these and refresh the documentation as we go.
- **References to Tutum remain** in the documentation. We will update these and refresh the documentation as we go
- **References to Tutum remain** in the documentation. We will update these and refresh the documentation as we go

7
docker-cloud/slack-integration.md
View File

@ -1,9 +1,8 @@
---
description: Integrate with Slack
keywords: Slack, integrate, notifications
redirect_from:
- /docker-cloud/tutorials/slack-integration/
description: Integrate with Slack
keywords:
- Slack, integrate, notifications
title: Set up Docker Cloud notifications in Slack
---
@ -47,4 +46,4 @@ Enjoy your new Slack channel integration!
* From the Slack **Notifications** section you can also change the channel that the integration posts to. Click the reload icon (two arrows) next to the Slack integration to reopen the OAuth channel selector.
* Alternately, go to the <a href="https://slack.com/apps/manage" target="_blank">Slack App Management page</a> and search for "Docker Cloud". Click the result to see all of the Docker Cloud notification channels set for the Slack team.
* Alternately, go to the <a href="https://slack.com/apps/manage" target="_blank">Slack App Management page</a> and search for "Docker Cloud". Click the result to see all of the Docker Cloud notification channels set for the Slack team.