tyler.durden/compose
1
0
Fork 0
mirror of https://github.com/docker/compose.git synced 2025-04-08 17:05:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request from mnowster/docs-for-extends-file-default-behaviour

Browse Source 
Docs for `file` default behaviour
This commit is contained in:
Aanand Prasad 2015-07-07 17:12:29 +01:00
commit a8ad13734e
2 changed files with 9 additions and 4 deletions

10
docs/extends.md

@ -233,11 +233,13 @@ manually keep both environments in sync.
### Reference
You can use `extends` on any service together with other configuration keys. It
always expects a dictionary that should always contain two keys: `file` and
`service`.
always expects a dictionary that should always contain the key: `service` and optionally the `file` key.
The `file` key specifies which file to look in. It can be an absolute path or a
relative one—if relative, it's treated as relative to the current file.
The `file` key specifies the location of a Compose configuration file defining
the extension. The `file` value can be an absolute or relative path. If you
specify a relative path, Docker Compose treats it as relative to the location
of the current file. If you don't specify a `file`, Compose looks in the
current configuration file.
The `service` key specifies the name of the service to extend, for example `web`
or `database`.

3
docs/yml.md

@ -217,6 +217,9 @@ and adds `ports` and `links` configuration. It overrides one of the defined
environment variables (DEBUG) with a new value, and the other one
(SEND_EMAILS) is left untouched.
The `file` key is optional, if it is not set then Compose will look for the
service within the current file.
For more on `extends`, see the [tutorial](extends.md#example) and
[reference](extends.md#reference).