LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

feat(server): start grpc server and register services in standalone mode (#18110)

Browse Source 
Co-authored-by: Marko <marko@baricevic.me>
This commit is contained in:
Philip Offtermatt
2023-10-18 10:32:53 +00:00
committed by GitHub
co-authored by Marko
parent 50f936f60e
commit 31f5bc07e9
3 changed files with 44 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user/run-node/01-run-node.md
+7
View File
@@ -157,6 +157,13 @@ The previous command allow you to run a single node. This is enough for the next
The naive way would be to run the same commands again in separate terminal windows. This is possible, however in the Cosmos SDK, we leverage the power of [Docker Compose](https://docs.docker.com/compose/) to run a localnet. If you need inspiration on how to set up your own localnet with Docker Compose, you can have a look at the Cosmos SDK's [`docker-compose.yml`](https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/docker-compose.yml).
### Standalone App/CometBFT
By default, the Cosmos SDK runs CometBFT in-process with the application
If you want to run the application and CometBFT in separate processes,
start the application with the `--with-comet=false` flag
and set `rpc.laddr` in `config.toml` to the CometBFT node's RPC address.
## Logging
Logging provides a way to see what is going on with a node. By default the info level is set. This is a global level and all info logs will be outputted to the terminal. If you would like to filter specific logs to the terminal instead of all, then setting `module:log_level` is how this can work.