Persistent state fix (#285)

main
Alejandro Martinez Andres 2021-12-21 20:46:28 +01:00 committed by GitHub
parent ad7ce8e3da
commit d68cf29e46
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 32 additions and 1 deletions

View File

@ -55,7 +55,7 @@ node.
### Single-Node Development Chain
This command will start the single-node development chain with persistent state:
This command will start the single-node development chain with non-persistent state:
```bash
./target/release/node-template --dev
@ -73,6 +73,37 @@ Start the development chain with detailed logging:
RUST_BACKTRACE=1 ./target/release/node-template -ldebug --dev
```
> Development chain means that the state of our chain will be in a tmp folder while the nodes are
> running. Also, **alice** account will be authority and sudo account as declared in the [genesis
> state](https://github.com/substrate-developer-hub/substrate-node-template/blob/main/node/src/
chain_spec.rs#L49). At the same time the following accounts will be prefunded:
> - Alice
> - Bob
> - Alice//stash
> - Bob//stash
In case of being interested in maintaining the chain' state between runs a base path must be added
so the db can be stored in the provided folder instead of a temporal one. We could use this folder
to store different chain databases, as a different folder will be created per different chain that
is ran. The following commands shows how to use a newly created folder as our db base path.
```bash
// Create a folder to use as the db base path
$ mkdir my-chain-state
// Use of that folder to store the chain state
$ ./target/release/node-template --dev --base-path ./my-chain-state/
// Check the folder structure created inside the base path after running the chain
$ ls ./my-chain-state
chains
$ ls ./my-chain-state/chains/
dev
$ ls ./my-chain-state/chains/dev
db keystore network
```
### Connect with Polkadot-JS Apps Front-end
Once the node template is running locally, you can connect it with **Polkadot-JS Apps** front-end