Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--dev flag implies --tmp #107

Merged
merged 1 commit into from
Oct 31, 2022
Merged
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion docs/faq/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ you compile a contract in `--release` mode.
1. __Set the log level of your node to `runtime::contracts=debug`.__<br/>
For example, to have only errors and debug output show up for the `substrate-contracts-node`:
```
substrate-contracts-node --dev --tmp -lerror,runtime::contracts=debug
substrate-contracts-node --dev -lerror,runtime::contracts=debug
```

__Important: Debug output is only printed for RPC calls or off-chain tests ‒ not for transactions!__
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/running.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ It's a comfortable option if you want to get a quickstart.
[After successfully installing `substrate-contracts-node`](/getting-started/setup), you can start a local development chain by running:

```bash
substrate-contracts-node --dev --tmp
substrate-contracts-node --dev
```

![An image of the terminal starting a Substrate node](./assets/start-substrate-node.png)
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ There is a known issue with the Substrate block production (BABE) on a running c
ClientImport("Unexpected epoch change")
```

To solve this you will need to restart your node with: `substrate-contracts-node --dev --tmp`. At that point, you will
To solve this you will need to restart your node with: `substrate-contracts-node --dev`. At that point, you will
need to re-deploy any contracts and re-do any steps that you may have done before on your node. As
long as you keep your node running, you should face no issues.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-4.0.0-alpha.1/faq/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ you compile a contract in `--release` mode.
1. __Set the log level of your node to `runtime::contracts=debug`.__<br/>
For example, to have only errors and debug output show up for the `substrate-contracts-node`:
```
substrate-contracts-node --dev --tmp -lerror,runtime::contracts=debug
substrate-contracts-node --dev -lerror,runtime::contracts=debug
```

__Important: Debug output is only printed for RPC calls or off-chain tests ‒ not for transactions!__
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ It's a comfortable option if you want to get a quickstart.
[After successfully installing `substrate-contracts-node`](/getting-started/setup), you can start a local development chain by running:

```bash
substrate-contracts-node --dev --tmp
substrate-contracts-node --dev
```

![An image of the terminal starting a Substrate node](./assets/start-substrate-node.png)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ There is a known issue with the Substrate block production (BABE) on a running c
ClientImport("Unexpected epoch change")
```

To solve this you will need to restart your node with: `substrate-contracts-node --dev --tmp`. At that point, you will
To solve this you will need to restart your node with: `substrate-contracts-node --dev`. At that point, you will
need to re-deploy any contracts and re-do any steps that you may have done before on your node. As
long as you keep your node running, you should face no issues.

Expand Down