trustchain-oc1-orchestral
/
devicehub-teal
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

change README

This commit is contained in:
Cayo Puigdefabregas 2023-09-28 17:57:56 +02:00
parent ac3d318fc9
commit ece944ea3f
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -42,6 +42,7 @@ You can use these parameters for default as a test, but you need to add values i
API_DLT_TOKEN
API_RESOLVER
```
You can use that .env as a default for a test deployment, but these variables need to be initialized. These values should come from a deployed [API_DLT connector](https://gitlab.com/dsg-upc/ereuse-dpp) service instance.
5. run the dockers:
```
@ -57,6 +58,14 @@ If the last line you see one text like this, *exited whit code*:
```
Then the install went wrong.
If the deployment was end-to-end successful (two running Devicehub instances successfully connected to the DLT backend selected in the .env file), you can see this text in the last lines:
```
devicehub-teal-devicehub-id-client-1 | * Running on http://172.28.0.2:5000/ (Press CTRL+C to quit)
devicehub-teal-devicehub-id-server-1 | * Running on all addresses.
devicehub-teal-devicehub-id-server-1 | WARNING: This is a development server. Do not use it in a production deployment.
devicehub-teal-devicehub-id-server-1 | * Running on http://172.28.0.5:5000/ (Press CTRL+C to quit)
```
6. If you want to down the volumes and remove the data, you can use:
```
docker compose down -v