Update docs; new local-setup/config and new integritee-dev docker image

4-development/4.9-dev-environment.md

@@ -20,10 +20,10 @@ Steps to get a running setup:
 
 1. Mount the current directory containing the integritee-worker and integritee node into the Docker container and start a bash session inside: 
 ```shell
-docker run -it --mount "type=bind,src=$(pwd),dst=/opt/shared" --workdir /opt/shared integritee/integritee-dev:0.1.10 /bin/bash
+docker run -it --mount "type=bind,src=$(pwd),dst=/opt/shared" --workdir /opt/shared integritee/integritee-dev:0.1.12 /bin/bash
 
 # If you want to expose the default ports of the services to the host, you can supply some `-p` args:
-docker run -it --mount "type=bind,src=$(pwd),dst=/opt/shared" --workdir /opt/shared -p 9944:9944 -p 2000:2000 -p 3443:3443 integritee/integritee-dev:0.1.10 /bin/bash
+docker run -it --mount "type=bind,src=$(pwd),dst=/opt/shared" --workdir /opt/shared -p 9944:9944 -p 2000:2000 -p 3443:3443 integritee/integritee-dev:0.1.12 /bin/bash
 ```
 2. Now you have access to the shell in the Docker container. So you can start the builds.
 ```shell
@@ -46,7 +46,7 @@ SGX_MODE=SW WORKER_MODE=offchain-worker make
 # The output file will be in the ./bin folder.
 
 # Then you can spawn two workers and the integritee-node with the launch script.
-./local-setup/launch.py ./local-setup/simple-config.json
+./local-setup/launch.py ./local-setup/config/two-workers.json
 
 # Enter the same Docker container with a bash session.
 docker exec -it <container-id> bash

5-nodes-and-infrastructure/5.2-how-to-set-up-and-run-a-sidechain-or-tocw-node/5.2.3-software-requirements/5.2.3.2-docker.md

@@ -5,13 +5,13 @@ We also provide docker images with all the tools installed, you can find them on
 Execute the following command to get the docker image.
 
 ```
-docker pull integritee/integritee-dev:0.1.9
+docker pull integritee/integritee-dev:0.1.12
 ```
 
 The following command enters the docker image and starts a bash session inside the container, mounting the current directory `pwd` into `/root/work` inside the docker image. Hence, we recommend running the command either in the SDK’s root directory or in its parent directory if you also want to mount other projects inside the docker container.
 
 ```
-docker run -it -v $(pwd):/root/work integritee/integritee-dev:0.1.9 /bin/bash
+docker run -it -v $(pwd):/root/work integritee/integritee-dev:0.1.12 /bin/bash
 ```
 
 It is useful to only stop the container instead of tearing it down in between sessions if you are developing because the cargo build cache is preserved. To restart and re-enter the docker container created above, you can execute the following command.

5-nodes-and-infrastructure/5.2-how-to-set-up-and-run-a-sidechain-or-tocw-node/5.2.3-software-requirements/5.2.3.3-enabling-sgx-hardware-support-in-docker.md

@@ -7,7 +7,7 @@ If you are on a platform that supports SGX, you can enable HW support by:
 * Start the docker with SGX device support:
 
 ```
-docker run -it -v $(pwd):/root/work --device /dev/isgx integritee/integritee-dev:0.1.9 /bin/bash
+docker run -it -v $(pwd):/root/work --device /dev/isgx integritee/integritee-dev:0.1.12 /bin/bash
 ```
 
 * Start the aesm service inside the docker: