Skip to content

Commit 5416c44

Browse files
authored
Update set-up-a-test-network.md (#2156)
Add cmd to copy the workers
1 parent 62a8157 commit 5416c44

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/md/en/docs/test/set-up-a-test-network.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ To prepare a working folder with the binaries for the test network:
5353
Release branches use the naming convention `release-v<n.n.n>`.
5454
For example, the release branch used in this tutorial is `release-v1.0.0`.
5555
You can check out a more recent release branch instead of using `release-v1.0.0`.
56-
You can find information about recent releases and what's included in each release on the [Releases](https://github.com/paritytech/polkadot/releases) tab.
56+
You can find information about recent releases and what's included in each release on the [Releases](https://github.com/paritytech/polkadot-sdk/releases) tab.
5757

5858
1. Change to the root of the `polkadot` directory by running the following command:
5959

@@ -69,10 +69,11 @@ To prepare a working folder with the binaries for the test network:
6969

7070
Compiling the node can take 15 to 60 minuets to complete.
7171

72-
1. Copy the Polkadot binary into your working `bin` folder by running a command similar to the following:
72+
1. Copy the Polkadot binary and workers into your working `bin` folder by running a command similar to the following:
7373

7474
```bash
7575
cp ./target/release/polkadot ../bin/polkadot-v1.0.0
76+
cp ./target/release/polkadot-*-worker ../bin/
7677
```
7778

7879
As this example illustrates, it's generally a good practice to append the version of `polkadot` to the binary name to keep the files in the `bin` folder organized.

0 commit comments

Comments
 (0)