Skip to content
This repository was archived by the owner on Jul 28, 2024. It is now read-only.

Conversation

@borekb
Copy link
Member

@borekb borekb commented Mar 9, 2019

Issue: #1389

To makes things cleaner, Docker Compose services have been split into two YAML files:

  • docker-compose.yml for development environment
  • docker-compose-tests.yml for tests

All testing npm scripts now start with docker-compose -f docker-compose-tests.yml ..., docs have been updated accordingly (preview).

borekb added 2 commits March 9, 2019 22:31
Details:

- package.json test scripts now run `docker-compose -f docker-compose-tests.yml ...`.
- Stopping dev env and testing env is now done via separate scripts, see `stop` vs. `tests:stop` and `stop-and-cleanup` vs. `tests:stop-and-cleanup`.
- Docker-compose examples now use the `-f` flag.
- `stop` → `tests:stop`, `stop-and-cleanup` → `tests:stop-and-cleanup`.
@borekb borekb added the scope: tests Testing code. For infrastructure (CI, etc.), use "dev-infrastructure". label Mar 9, 2019
@borekb borekb added this to the 4.0 milestone Mar 9, 2019
@borekb borekb self-assigned this Mar 9, 2019
@borekb borekb added the scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc. label Mar 9, 2019
@borekb borekb merged commit 618813b into master Mar 9, 2019
@borekb borekb deleted the 1389-separate-docker-compose-files branch March 9, 2019 22:04
@borekb borekb changed the title Separate docker-compose files for dev env vs. tests Separate docker-compose files for dev and tests Apr 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc. scope: tests Testing code. For infrastructure (CI, etc.), use "dev-infrastructure".

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants