Skip to content

Commit

Permalink
Fix error in docs about ddev compose-config (#1478)
Browse files Browse the repository at this point in the history
  • Loading branch information
rfay committed Mar 4, 2019
1 parent e7c0133 commit ba27311
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions cmd/ddev/cmd/compose-config_test.go
Expand Up @@ -38,7 +38,7 @@ func TestComposeConfigCmd(t *testing.T) {
_, err := exec.RunCommand(DdevBin, args)
assert.NoError(t, err)

// Ensure ddev compose-config works as expected
// Ensure ddev debug compose-config works as expected
args = []string{"debug", "compose-config"}
out, err := exec.RunCommand(DdevBin, args)
assert.NoError(t, err)
Expand All @@ -49,7 +49,7 @@ func TestComposeConfigCmd(t *testing.T) {
err = ioutil.WriteFile(overrideFile, []byte(override), 0644)
assert.NoError(t, err)

// Ensure ddev compose-config includes override values
// Ensure ddev debug compose-config includes override values
args = []string{"debug", "compose-config"}
out, err = exec.RunCommand(DdevBin, args)
assert.NoError(t, err)
Expand Down
2 changes: 1 addition & 1 deletion docs/users/extend/custom-compose-files.md
Expand Up @@ -16,7 +16,7 @@ The main docker-compose.yaml file is exclusively reserved for ddev's use, and wi

## Confirming docker-compose configurations

To better understand how ddev is parsing your custom docker-compose files, you can run `ddev compose-config` to print the final docker-compose configuration as generated by ddev when starting your project.
To better understand how ddev is parsing your custom docker-compose files, you can run `ddev debug compose-config` to print the final docker-compose configuration as generated by ddev when starting your project.

## Conventions for defining additional services

Expand Down

0 comments on commit ba27311

Please sign in to comment.