Skip to content

Commit 64e6512

Browse files
scjanejohndmulhausen
authored andcommitted
Update service-links.md (docker#2529)
1 parent 76a9be1 commit 64e6512

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docker-cloud/apps/service-links.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ functionality using directional links recorded in environment variables.
9696
When you link a "client" service to a "server" service, Docker Cloud performs
9797
the following actions on the "client" service:
9898

99-
1. Creates a group of environment variables that contain information about the exposed ports of the "server" service, including its IP address, port and protocol.
99+
1. Creates a group of environment variables that contain information about the exposed ports of the "server" service, including its IP address, port, and protocol.
100100

101101
2. Copies all of the "server" service environment variables to the "client" service with an `HOSTNAME_ENV_` prefix.
102102

@@ -164,7 +164,7 @@ This example snippet creates a directional link from `my-proxy` to `my-web-app`,
164164

165165
### DNS hostnames vs service links
166166

167-
> **Note**: Hostnames are updated during runtime if the service scales up or down. Environment variables are only set or updated at deploy or redeploy. If your services will scale up or down frequently, you should use hostnames rather than service links.
167+
> **Note**: Hostnames are updated during runtime if the service scales up or down. Environment variables are only set or updated at deploy or redeploy. If your services will scale up or down frequently, you should use hostnames rather than service links.
168168

169169
In the example, the `my-proxy` containers can access the service links using following hostnames:
170170

0 commit comments

Comments
 (0)