Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: migrate from docker-compose v1 to docker compose v2 #260

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,10 +122,10 @@ The app have two npm scripts for adding a new customer:

Run either of the two scripts using `npm run <name>`.

If running inside docker, you can run it using `docker-compose`, e.g:
If running inside docker, you can run it using `docker compose`, e.g:

```
docker-compose exec opbeans-node npm run customer-add-redos
docker compose exec opbeans-node npm run customer-add-redos
```

## License
Expand Down
6 changes: 3 additions & 3 deletions tests/tests.bats
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,12 @@ CONTAINER="opbeans-node"

@test "build image" {
cd $BATS_TEST_DIRNAME/..
run docker-compose build
run docker compose build
assert_success
}

@test "create test container" {
run docker-compose up -d
run docker compose up -d
assert_success
}

Expand All @@ -32,6 +32,6 @@ CONTAINER="opbeans-node"
}

@test "clean test containers" {
run docker-compose down
run docker compose down
assert_success
}