Skip to content

Commit

Permalink
Update set-up-a-test-network.md
Browse files Browse the repository at this point in the history
Add cmd to copy the workers
  • Loading branch information
pepoviola authored Jun 2, 2024
1 parent 62a8157 commit f842d36
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions content/md/en/docs/test/set-up-a-test-network.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ To prepare a working folder with the binaries for the test network:
Release branches use the naming convention `release-v<n.n.n>`.
For example, the release branch used in this tutorial is `release-v1.0.0`.
You can check out a more recent release branch instead of using `release-v1.0.0`.
You can find information about recent releases and what's included in each release on the [Releases](https://github.com/paritytech/polkadot/releases) tab.
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.

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

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

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

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

```bash
cp ./target/release/polkadot ../bin/polkadot-v1.0.0
cp ./target/release/polkadot-*-worker ../bin/
```

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.
Expand Down

0 comments on commit f842d36

Please sign in to comment.