Skip to content
This repository has been archived by the owner on Aug 2, 2024. It is now read-only.

docs: fix setup and run commands in getting-started.md #1186

Merged
merged 1 commit into from
Oct 12, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,25 +16,25 @@ rustup show
Use Rust's native `cargo` command to build and launch the template node:

```sh
cargo run --release -- setup
cargo run --release -- run --dev
cargo run --release -- setup --chain=dev --from-remote
cargo run --release -- --dev
```

The node also supports to use manual seal (to produce block manually through
RPC). This is also used by the typescript tests:

```sh
$ cargo run --release -- run --dev --sealing=manual
$ cargo run --release -- --dev --sealing=manual
# Or
$ cargo run --release -- run --dev --sealing=instant
$ cargo run --release -- --dev --sealing=instant
```

Log level can be specified with `-l` flag. For example, `-ldebug` will show
debug logs. It can also be specified via the `RUST_LOG` environment variable.
For example:

```sh
RUSTLOG=runtime=info cargo run --release -- run --dev
RUSTLOG=runtime=info cargo run --release -- --dev
```

### Cargo Build
Expand Down Expand Up @@ -81,7 +81,7 @@ This command will start the single-node development chain with non-persistent
state:

```bash
./target/release/madara setup
./target/release/madara setup --chain=dev --from-remote
./target/release/madara --dev
```

Expand Down
Loading