From f842d3616273d10f416d5cce8a31a7ad7fade5b3 Mon Sep 17 00:00:00 2001 From: Javier Viola <363911+pepoviola@users.noreply.github.com> Date: Sun, 2 Jun 2024 11:07:51 +0200 Subject: [PATCH] Update set-up-a-test-network.md Add cmd to copy the workers --- content/md/en/docs/test/set-up-a-test-network.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/md/en/docs/test/set-up-a-test-network.md b/content/md/en/docs/test/set-up-a-test-network.md index 301a37003..7f6c2013c 100644 --- a/content/md/en/docs/test/set-up-a-test-network.md +++ b/content/md/en/docs/test/set-up-a-test-network.md @@ -53,7 +53,7 @@ To prepare a working folder with the binaries for the test network: Release branches use the naming convention `release-v`. 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: @@ -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.