Skip to content

Commit e91ae0e

Browse files
committed
docs: modify snapshot example
1 parent d734aa0 commit e91ae0e

2 files changed

Lines changed: 8 additions & 5 deletions

File tree

docs/fabric/EXAMPLE-EN.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -856,7 +856,7 @@ choose
856856
- Channel Name : test
857857
- Block Number : 0 (execute snapshot immediately) or N (execute snapshot after N blocks)
858858
859-
p.s. The completed snapshot will be mounted to host under $.bdk/fabric/${networkName}/channel-artifacts/snapshots/${peerContainerName}/completed/${channelName}/${blockHeight}
859+
p.s. The completed snapshot will be copied to host under .bdk/fabric/{networkName}/peerOrganizations/{domain}/peers/peer{number}.{domain}/snapshots/completed/{channelName}/{blockHeight}
860860
861861
### Step 2 (Optional) : Check submitted snapshot requests
862862
@@ -905,11 +905,12 @@ bdk fabric channel snapshot -i
905905
906906
choose
907907
- Operation : joinBySnapshot
908-
- Snapshot Path : .bdk/fabric/bdk-fabric-network/channel-artifacts/snapshots/peer0.org0.example.com/completed/test/1/ (Example) (Enter the absolute path of the snapshot directory mounted locally)
908+
- Snapshot Path : $.bdk/fabric/bdk-fabric-network/peerOrganizations/org0.example.com/peers/peer0.org0.example.com/snapshots/completed/test/0/ (Example) (Enter the absolute path of the snapshot directory on host)
909909
910910
### Step 5: Verify whether the new peer has joined the channel successfully
911911
912912
```bash
913-
# Inside peer0.org1.example.com's container, run `peer channel list` to check if it has joined
913+
# Inside peer0.org1.example.com's container, run `peer channel list or peer channel getinfo` to check if it has joined
914914
peer channel list
915+
peer channel getinfo -c {channelName}
915916
```

docs/fabric/EXAMPLE.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -840,6 +840,7 @@ bdk fabric channel snapshot -i
840840
- Operation : submitRequest
841841
- Channel Name : test
842842
- Block Number : 0 (立即執行 snapshot) or N (N個block後再執行 snapshot)
843+
p.s. 完成的快照會被複製到本地端的 .bdk/fabric/{networkName}/peerOrganizations/{domain}/peers/peer{number}.{domain}/snapshots/completed/{channelName}/{blockHeight} 下
843844

844845
### Step 2 (Optional) : 查看已提交的 snapshot request
845846
```bash
@@ -888,11 +889,12 @@ bdk fabric channel snapshot -i
888889

889890
選擇
890891
- Operation : joinBySnapshot
891-
- Snapshot Path : .bdk/fabric/bdk-fabric-network/channel-artifacts/snapshots/peer0.org0.example.com/completed/test/1/ (範例)(輸入被mount在本地的snapshot目錄的絕對路徑
892+
- Snapshot Path : .bdk/fabric/bdk-fabric-network/peerOrganizations/org0.example.com/peers/peer0.org0.example.com/snapshots/completed/test/0/ (範例)(輸入被copy在本地的snapshot目錄的絕對路徑
892893

893894
### Step 5 : 確認新的 peer 是否加入 channel
894895

895896
```bash
896-
# 到 peer0.org1.example.com 的 container 內下指令 peer channel list 查看是否已被加入 channel
897+
# 到 peer0.org1.example.com 的 container 內下指令 peer channel list 或 peer channel getinfo 查看是否已被加入 channel
897898
peer channel list
899+
peer channel getinfo -c {channelName}
898900
```

0 commit comments

Comments
 (0)