Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 27d00ce

Browse files
johndmulhausenjohndmulhausen
authored
Merge pull request docker#418 from aduermael/absolute-links
absolute links to docs.docker.com are now relative links
2 parents ab8bcb7 + 8fa5f3a commit 27d00ce

File tree

71 files changed

+126
-126
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

71 files changed

+126
-126
lines changed

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ You have three options:
107107
```
108108

109109
If you haven't got Docker Compose installed,
110-
[follow these installation instructions](https://docs.docker.com/compose/install/).
110+
[follow these installation instructions](/compose/install/).
111111
112112
The container runs in the background and incrementally rebuilds the site each
113113
time a file changes. You can keep your browser open to http://localhost:4000/
@@ -150,7 +150,7 @@ directly on docs.docker.com.
150150
## Style guide
151151
152152
If you have questions about how to write for Docker's documentation, please see
153-
the [style guide](https://docs.docker.com/opensource/doc-style/). The style guide provides
153+
the [style guide](/opensource/doc-style/). The style guide provides
154154
guidance about grammar, syntax, formatting, styling, language, or tone. If
155155
something isn't clear in the guide, please submit an issue to let us know or
156156
submit a pull request to help us improve it.

‎compose/bundles.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ Wrote bundle to vossibility-stack.dab
5454
> you need to install an experimental build of Docker Engine to use it.
5555
>
5656
> If you're on Mac or Windows, download the “Beta channel” version of
57-
> [Docker for Mac](https://docs.docker.com/docker-for-mac/) or
58-
> [Docker for Windows](https://docs.docker.com/docker-for-windows/) to install
57+
> [Docker for Mac](/docker-for-mac/) or
58+
> [Docker for Windows](/docker-for-windows/) to install
5959
> it. If you're on Linux, follow the instructions in the
6060
> [experimental build README](https://github.com/docker/docker/blob/master/experimental/README.md).
6161

‎compose/compose-file.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ Override the default command.
171171

172172
command: bundle exec thin -p 3000
173173

174-
The command can also be a list, in a manner similar to [dockerfile](https://docs.docker.com/engine/reference/builder/#cmd):
174+
The command can also be a list, in a manner similar to [dockerfile](/engine/reference/builder/#cmd):
175175

176176
command: [bundle, exec, thin, -p, 3000]
177177

@@ -264,7 +264,7 @@ Override the default entrypoint.
264264

265265
entrypoint: /code/entrypoint.sh
266266

267-
The entrypoint can also be a list, in a manner similar to [dockerfile](https://docs.docker.com/engine/reference/builder/#entrypoint):
267+
The entrypoint can also be a list, in a manner similar to [dockerfile](/engine/reference/builder/#entrypoint):
268268

269269
entrypoint:
270270
- php
@@ -413,7 +413,7 @@ options and tags it with the specified tag.
413413
414414
### labels
415415

416-
Add metadata to containers using [Docker labels](https://docs.docker.com/engine/userguide/labels-custom-metadata/). You can use either an array or a dictionary.
416+
Add metadata to containers using [Docker labels](/engine/userguide/labels-custom-metadata/). You can use either an array or a dictionary.
417417

418418
It's recommended that you use reverse-DNS notation to prevent your labels from conflicting with those used by other software.
419419

@@ -462,7 +462,7 @@ Logging configuration for the service.
462462

463463
The `driver` name specifies a logging driver for the service's
464464
containers, as with the ``--log-driver`` option for docker run
465-
([documented here](https://docs.docker.com/engine/reference/logging/overview/)).
465+
([documented here](/engine/reference/logging/overview/)).
466466

467467
The default value is json-file.
468468

@@ -721,8 +721,8 @@ use the specified driver.
721721
> Note: No path expansion will be done if you have also specified a
722722
> `volume_driver`.
723723
724-
See [Docker Volumes](https://docs.docker.com/engine/userguide/dockervolumes/) and
725-
[Volume Plugins](https://docs.docker.com/engine/extend/plugins_volume/) for more
724+
See [Docker Volumes](/engine/userguide/dockervolumes/) and
725+
[Volume Plugins](/engine/extend/plugins_volume/) for more
726726
information.
727727

728728
### volumes_from
@@ -749,7 +749,7 @@ then read-write will be used.
749749
### cpu\_shares, cpu\_quota, cpuset, domainname, hostname, ipc, mac\_address, mem\_limit, memswap\_limit, privileged, read\_only, restart, shm\_size, stdin\_open, tty, user, working\_dir
750750

751751
Each of these is a single value, analogous to its
752-
[docker run](https://docs.docker.com/engine/reference/run/) counterpart.
752+
[docker run](/engine/reference/run/) counterpart.
753753

754754
cpu_shares: 73
755755
cpu_quota: 50000
@@ -781,7 +781,7 @@ While it is possible to declare volumes on the fly as part of the service
781781
declaration, this section allows you to create named volumes that can be
782782
reused across multiple services (without relying on `volumes_from`), and are
783783
easily retrieved and inspected using the docker command line or API.
784-
See the [docker volume](https://docs.docker.com/engine/reference/commandline/volume_create/)
784+
See the [docker volume](/engine/reference/commandline/volume_create/)
785785
subcommand documentation for more information.
786786

787787
### driver

‎compose/networking.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ title: Networking in Compose
1414
> **Note:** This document only applies if you're using [version 2 of the Compose file format](compose-file.md#versioning). Networking features are not supported for version 1 (legacy) Compose files.
1515
1616
By default Compose sets up a single
17-
[network](https://docs.docker.com/engine/reference/commandline/network_create/) for your app. Each
17+
[network](/engine/reference/commandline/network_create/) for your app. Each
1818
container for a service joins the default network and is both *reachable* by
1919
other containers on that network, and *discoverable* by them at a hostname
2020
identical to the container name.
@@ -77,11 +77,11 @@ See the [links reference](compose-file.md#links) for more information.
7777

7878
When [deploying a Compose application to a Swarm cluster](swarm.md), you can make use of the built-in `overlay` driver to enable multi-host communication between containers with no changes to your Compose file or application code.
7979

80-
Consult the [Getting started with multi-host networking](https://docs.docker.com/engine/userguide/networking/get-started-overlay/) to see how to set up a Swarm cluster. The cluster will use the `overlay` driver by default, but you can specify it explicitly if you prefer - see below for how to do this.
80+
Consult the [Getting started with multi-host networking](/engine/userguide/networking/get-started-overlay/) to see how to set up a Swarm cluster. The cluster will use the `overlay` driver by default, but you can specify it explicitly if you prefer - see below for how to do this.
8181

8282
## Specifying custom networks
8383

84-
Instead of just using the default app network, you can specify your own networks with the top-level `networks` key. This lets you create more complex topologies and specify [custom network drivers](https://docs.docker.com/engine/extend/plugins_network/) and options. You can also use it to connect services to externally-created networks which aren't managed by Compose.
84+
Instead of just using the default app network, you can specify your own networks with the top-level `networks` key. This lets you create more complex topologies and specify [custom network drivers](/engine/extend/plugins_network/) and options. You can also use it to connect services to externally-created networks which aren't managed by Compose.
8585

8686
Each service can specify what networks to connect to with the *service-level* `networks` key, which is a list of names referencing entries under the *top-level* `networks` key.
8787

‎compose/overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,4 +184,4 @@ individuals, we have a number of open channels for communication.
184184

185185
* To contribute code or documentation changes: please submit a [pull request on Github](https://github.com/docker/compose/pulls).
186186

187-
For more information and resources, please visit the [Getting Help project page](https://docs.docker.com/opensource/get-help/).
187+
For more information and resources, please visit the [Getting Help project page](/opensource/get-help/).

‎compose/swarm.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,10 @@ format](compose-file.md#versioning) you are using:
2525

2626
- subject to the [limitations](swarm.md#limitations) described below,
2727

28-
- as long as the Swarm cluster is configured to use the [overlay driver](https://docs.docker.com/engine/userguide/networking/dockernetworks/#an-overlay-network),
28+
- as long as the Swarm cluster is configured to use the [overlay driver](/engine/userguide/networking/dockernetworks/#an-overlay-network),
2929
or a custom driver which supports multi-host networking.
3030

31-
Read [Get started with multi-host networking](https://docs.docker.com/engine/userguide/networking/get-started-overlay/) to see how to
31+
Read [Get started with multi-host networking](/engine/userguide/networking/get-started-overlay/) to see how to
3232
set up a Swarm cluster with [Docker Machine](/machine/overview.md) and the overlay driver. Once you've got it running, deploying your app to it should be as simple as:
3333

3434
$ eval "$(docker-machine env --swarm <name of swarm master machine>)"

‎compose/wordpress.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ This pulls the needed images, and starts the wordpress and database containers,
9494
9595
### Bring up WordPress in a web browser
9696
97-
If you're using [Docker Machine](https://docs.docker.com/machine/), then `docker-machine ip MACHINE_VM` gives you the machine address and you can open `http://MACHINE_VM_IP:8000` in a browser.
97+
If you're using [Docker Machine](/machine/), then `docker-machine ip MACHINE_VM` gives you the machine address and you can open `http://MACHINE_VM_IP:8000` in a browser.
9898
9999
At this point, WordPress should be running on port `8000` of your Docker Host, and you can complete the "famous five-minute installation" as a WordPress administrator.
100100

‎cs-engine/release-notes/prior-release-notes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -340,5 +340,5 @@ Because this addition is preventative, no CVE-ID is requested.
340340
## CS Engine 1.6.0-cs2
341341
(23 Apr 2015)
342342

343-
First release, see the [Docker Engine 1.6.0 Release notes](https://docs.docker.com/v1.6/release-notes/)
343+
First release, see the [Docker Engine 1.6.0 Release notes](/v1.6/release-notes/)
344344
for more details.

‎docker-cloud/apps/ports.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ title: Publish and expose service or container ports
1212

1313
# Publish and expose service or container ports
1414

15-
In Docker Cloud you can **publish** or **expose** ports in services and containers, just like you can in Docker Engine (as documented [here](https://docs.docker.com/reference/run/#expose-incoming-ports) ).
15+
In Docker Cloud you can **publish** or **expose** ports in services and containers, just like you can in Docker Engine (as documented [here](/reference/run/#expose-incoming-ports) ).
1616

1717
* **Exposed ports** are ports that a container or service is using either to
1818
provide a service, or listen on. By default, exposed ports in Docker Cloud are

‎docker-cloud/apps/service-links.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Docker Cloud creates a per-user overlay network which connects all containers ac
1717
Docker Cloud gives your containers two ways find other services:
1818

1919
* Using service and container names directly as **hostnames**
20-
* Using **service links**, which are based on [Docker Compose links](https://docs.docker.com/compose/compose-file/#links)
20+
* Using **service links**, which are based on [Docker Compose links](/compose/compose-file/#links)
2121

2222
**Service and Container Hostnames** update automatically when a service scales up or down or redeploys. As a user, you can configure service names, and Docker Cloud uses these names to find the IP of the services and containers for you. You can use hostnames in your code to provide abstraction that allows you to easily swap service containers or components.
2323

@@ -55,7 +55,7 @@ If the container making the query is part of a stack, and there is a local match
5555
5656
## Using service links for service discovery
5757

58-
Docker Cloud's service linking is modeled on [Docker Compose links](https://docs.docker.com/compose/compose-file/#links) to provide a basic service discovery functionality using directional links recorded in environment variables.
58+
Docker Cloud's service linking is modeled on [Docker Compose links](/compose/compose-file/#links) to provide a basic service discovery functionality using directional links recorded in environment variables.
5959

6060
When you link a "client" service to a "server" service, Docker Cloud performs the following actions on the "client" service:
6161

0 commit comments

Comments
 (0)