Vaclav Pavlin b9892120b9 chore(docs): fix docs and mark some as deprecated (#1754)
* chore(docs): fix docs and mark some as deprecated

* Update docs/contributors/continuous-integration.md

Co-authored-by: Ivan Folgueira Bande <128452529+Ivansete-status@users.noreply.github.com>

* Update examples/v2/README.md

Co-authored-by: Ivan Folgueira Bande <128452529+Ivansete-status@users.noreply.github.com>

* mark TODO with date

* replace nim-waku with nwaku in docs

---------

Co-authored-by: Ivan Folgueira Bande <128452529+Ivansete-status@users.noreply.github.com>
2023-05-25 13:37:49 +02:00

1.8 KiB

Overview: running a nwaku node

This guide provides on overview for newcomers on how to build and run a nwaku node for the most common use cases. For a more advanced configuration see our configuration guides

To set up a nwaku node on a DigitalOcean droplet, refer to our quickstart guide for droplets. If you prefer running nwaku in Docker container, see our Docker guide.

1. Build

Build the nwaku node or download a precompiled binary from our releases page. Docker images are published to statusteam/nim-waku on Docker Hub. See our Docker quickstart guide to run nwaku in a Docker container.

2. Run

Run the nwaku node using a default or common configuration or configure the node for more advanced use cases.

Connect the nwaku node to other peers to start communicating.

3. Interact

A running nwaku node can be interacted with using the Waku v2 JSON RPC API.

Note: Private and Admin API functionality are disabled by default. To configure a nwaku node with these enabled, use the --rpc-admin:true and --rpc-private:true CLI options.

curl -d '{"jsonrpc":"2.0","method":"get_waku_v2_debug_v1_info","params":[],"id":1}' -H 'Content-Type: application/json' localhost:8546 -s | jq

Or using the Waku v2 HTTP REST API:

Note: REST API functionality is in ALPHA and therefore it is disabled by default. To configure a nwaku node with this enabled, use the --rest:true CLI option.

curl http://localhost:8546/debug/v1/info -s | jq