@@ -218,22 +218,22 @@ Leaving `docker stats` running in a terminal is often useful to see which contai
* Standard:
1. To build/rebuild images after code changes, from the `purpleteam-orchestrator/` root directory, run the following command:
```shell
npm run dc-build
```
```shell
npm run dc-build
```
2. From the `purpleteam-orchestrator/` root directory, run the following command:
```shell
npm run dc-up
```
```shell
npm run dc-up
```
* Debug (orchestrator or app-scanner. For this example we demo orchestrator, for app-scanner just swap the `orchestrator` with `app`):
1. To build/rebuild images after code changes, from the `purpleteam-orchestrator/` root directory, run the following command:
```shell
npm run dc-build-debug-orchestrator
```
```shell
npm run dc-build-debug-orchestrator
```
2. From the `purpleteam-orchestrator/` root directory, run the following command:
```shell
npm run dc-up-debug-orchestrator
```
```shell
npm run dc-up-debug-orchestrator
```
* Now you can attach to the `purpleteam-orchestrator`, or `purpleteam-app-scanner` process within the container. Further details in the [Debugging](#debugging) section
