diff --git a/developers/developer-guides/tools/clis/weave-cli/initia-node.mdx b/developers/developer-guides/tools/clis/weave-cli/initia-node.mdx index 34c18a70..5930891a 100644 --- a/developers/developer-guides/tools/clis/weave-cli/initia-node.mdx +++ b/developers/developer-guides/tools/clis/weave-cli/initia-node.mdx @@ -39,23 +39,20 @@ the node using `weave initia start`. - ```bash - weave initia start - ``` + {`weave initia start`} **Available Flags** Whether to run the node in the background. - -```bash weave initia stop ``` - -```bash weave initia restart ``` - + + {`weave initia stop`} + + + {`weave initia restart`} + - ```bash - weave initia log - ``` + {`weave initia log`} **Available Flags** The number of lines to display from the end of the logs. diff --git a/developers/developer-guides/tools/clis/weave-cli/rollup/launch.mdx b/developers/developer-guides/tools/clis/weave-cli/rollup/launch.mdx index e277ddd3..b8232750 100644 --- a/developers/developer-guides/tools/clis/weave-cli/rollup/launch.mdx +++ b/developers/developer-guides/tools/clis/weave-cli/rollup/launch.mdx @@ -65,7 +65,7 @@ weave rollup launch --with-config --vm - ```bash weave rollup start ``` + {`weave rollup start`} Note that `launch` command already starts the rollup node for you. This command is only needed if you have stopped the node and want to start it @@ -76,10 +76,15 @@ weave rollup launch --with-config --vm Whether to run the rollup node in the background. - ```bash weave rollup stop ``` - ```bash weave rollup restart ``` + + {`weave rollup stop`} + + + {`weave rollup restart`} + - ```bash weave rollup log ``` **Available Flags** + {`weave rollup log`} + **Available Flags** The number of lines to display from the end of the logs. diff --git a/developers/developer-guides/tools/clis/weave-cli/rollup/opinit-bots.mdx b/developers/developer-guides/tools/clis/weave-cli/rollup/opinit-bots.mdx index 73a92076..4815f575 100644 --- a/developers/developer-guides/tools/clis/weave-cli/rollup/opinit-bots.mdx +++ b/developers/developer-guides/tools/clis/weave-cli/rollup/opinit-bots.mdx @@ -20,20 +20,14 @@ You can also specify the bot type directly: - ```bash - weave opinit init executor - ``` + {`weave opinit init executor`} To set up Executor from the [config file](https://github.com/initia-labs/opinit-bots/blob/main/executor/README.md) without going through the interactive setup process, use the `--with-config` flag together with either `--generate-key-file` or `--key-file` flags. For example, to let Weave generate Executor's keys for you, use the following command: - ```bash - weave opinit init executor --with-config --generate-key-file - ``` + {`weave opinit init executor --with-config --generate-key-file`} To provide your own keys, use the following command: - ```bash - weave opinit init executor --with-config --key-file - ``` + {`weave opinit init executor --with-config --key-file `} **Available Flags** @@ -57,20 +51,14 @@ You can also specify the bot type directly: - ```bash - weave opinit init challenger - ``` + {`weave opinit init challenger`} To set up Challenger from the [config file](https://github.com/initia-labs/opinit-bots/blob/main/challenger/README.md) without going through the interactive setup process, use the `--with-config` flag together with either `--generate-key-file` or `--key-file` flags. For example, to let Weave generate Challenger's keys for you, use the following command: - ```bash - weave opinit init challenger --with-config --generate-key-file - ``` + {`weave opinit init challenger --with-config --generate-key-file`} To provide your own OPinit bot keys, use the following command: - ```bash - weave opinit init challenger --with-config --key-file - ``` + {`weave opinit init challenger --with-config --key-file `} **Available Flags** @@ -128,20 +116,14 @@ For rollups with built-in oracle enabled, set up the Oracle Executor key. - Reset Executor's database. This will clear all the data stored in the Executor's database (the configuration files are not affected). - - ```bash - weave opinit reset executor - ``` - + Reset Executor's database. This will clear all the data stored in the + Executor's database (the configuration files are not affected). + {`weave opinit reset executor`} - Reset Challenger's database. This will clear all the data stored in the Challenger's database (the configuration files are not affected). - - ```bash - weave opinit reset challenger - ``` - + Reset Challenger's database. This will clear all the data stored in the + Challenger's database (the configuration files are not affected). + {`weave opinit reset challenger`} @@ -151,15 +133,21 @@ For rollups with built-in oracle enabled, set up the Oracle Executor key. - ```bash weave opinit start executor ``` **Available Flags** + {`weave opinit start executor`} + **Available Flags** Whether to run the Executor in the background. - ```bash weave opinit stop executor ``` - ```bash weave opinit restart executor ``` + + {`weave opinit stop executor`} + + + {`weave opinit restart executor`} + - ```bash weave opinit log executor ``` **Available Flags** + {`weave opinit log executor`} + **Available Flags** The number of lines to display from the end of the Executor's logs. @@ -169,15 +157,21 @@ For rollups with built-in oracle enabled, set up the Oracle Executor key. - ```bash weave opinit start challenger ``` **Available Flags** + {`weave opinit start challenger`} + **Available Flags** Whether to run the node in the background. - ```bash weave opinit stop challenger ``` - ```bash weave opinit restart challenger ``` + + {`weave opinit stop challenger`} + + + {`weave opinit restart challenger`} + - ```bash weave opinit log challenger ``` **Available Flags** + {`weave opinit log challenger`} + **Available Flags** The number of lines to display from the end of the logs.