Fix error in full-stack-asset-transfer-guide docs

- Set correct CERTIFICATE file name in application ChaincodeEvents exercise.
- Add required environment variables to application AssetTransfer exercise, rather than rely on the RunApplication exercise being run in the same terminal first.

Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
This commit is contained in:
Mark S. Lewis 2023-05-02 16:49:55 +01:00 committed by Dave Enyeart
parent 74c48ec5aa
commit 628331d1a2
2 changed files with 9 additions and 1 deletions

View file

@ -12,6 +12,14 @@ There is already a **transfer** command implemented in [transfer.ts](../../appli
```
> **Tip:** You can also leave `npm run build:watch` running in a terminal window to automatically rebuild your application on any code change.
1. If you are using a new terminal window, set environment variables to point to resources required by the application.
```bash
export ENDPOINT=org1peer-api.127-0-0-1.nip.io:8080
export MSP_ID=org1MSP
export CERTIFICATE=../../_cfg/uf/_msp/org1/org1admin/msp/signcerts/cert.pem
export PRIVATE_KEY=../../_cfg/uf/_msp/org1/org1admin/msp/keystore/cert_sk
```
1. Try it out! Use the **transfer** command to transfer assets to new owners with the same MSP ID.
1. What happens if you try to manipulate (transfer, delete) an asset after transferring it to another MSP ID?

View file

@ -9,7 +9,7 @@ It is assumed that you have already built the application in prior steps.
```bash
export ENDPOINT=org1peer-api.127-0-0-1.nip.io:8080
export MSP_ID=org1MSP
export CERTIFICATE=../../_cfg/uf/_msp/org1/org1admin/msp/signcerts/org1admin.pem
export CERTIFICATE=../../_cfg/uf/_msp/org1/org1admin/msp/signcerts/cert.pem
export PRIVATE_KEY=../../_cfg/uf/_msp/org1/org1admin/msp/keystore/cert_sk
```