Skip to content

Commit

Permalink
Excavator: Render CircleCI file using template specified in .circleci…
Browse files Browse the repository at this point in the history
…/template.sh (#297)

* Excavator: Render CircleCI file using template specified in .circleci/template.sh

* fix
  • Loading branch information
svc-excavator-bot authored and iamdanfox committed Nov 22, 2019
1 parent b0d1b3f commit f07795c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 3 additions & 0 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -215,6 +215,9 @@ workflows:
requires: [ compile ]
filters: { tags: { only: /.*/ } }

- markdown:
filters: { tags: { only: /.*/ } }

- trial-publish:
requires: [ compile ]

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Accessing services in containers from outside a container

In tests it is likely services inside containers will need to be accessed in order to assert that they are behaving correctly. In addition, when tests run on Mac the Docker containers will be inside a Virtual Box machine and so must be accessed on an external IP address rather than the loopback interface.

It is recommended to only specify internal ports in the `docker-compose.yml` as described in the [https://docs.docker.com/compose/compose-file/#ports](reference). This makes tests independent of the environment on the host machine and of each other. Docker will then randomly allocate an external port. For example:
It is recommended to only specify internal ports in the `docker-compose.yml` as described in the (reference)[https://docs.docker.com/compose/compose-file/#ports]. This makes tests independent of the environment on the host machine and of each other. Docker will then randomly allocate an external port. For example:

```yaml
postgres:
Expand Down

0 comments on commit f07795c

Please sign in to comment.