logos-messaging/docs.waku.org
1
0
Fork 0
mirror of https://github.com/logos-messaging/docs.waku.org.git synced 2026-01-04 05:43:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: switch wakuv2 fleet to waku (#181)

Browse Source
This commit is contained in:
Anton Iakimov 2024-03-17 20:29:48 +01:00 committed by GitHub
parent 4ecfd9b703
commit 893cb1c492
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guides/nwaku/configure-discovery.md
View File

@ -51,7 +51,7 @@ For example, consider a `nwaku` node that enables `DNS Discovery`, connects to a
```shell ```shell
./build/wakunode2 \ ./build/wakunode2 \
--dns-discovery=true \ --dns-discovery=true \
--dns-discovery-url=enrtree://ANEDLO25QVUGJOUTQFRYKWX6P4Z4GKVESBMHML7DZ6YK4LGS5FC5O@prod.wakuv2.nodes.status.im \ --dns-discovery-url=enrtree://AIRVQ5DDA4FFWLRBCHJWUWOO6X6S4ZTZ5B667LQ6AJU6PEYDLRD5O@sandbox.waku.nodes.status.im \
--dns-discovery-name-server=8.8.8.8 \ --dns-discovery-name-server=8.8.8.8 \
--dns-discovery-name-server=8.8.4.4 --dns-discovery-name-server=8.8.4.4
``` ```

6
docs/guides/nwaku/configure-nwaku.md
View File

@ -75,7 +75,7 @@ You can configure `nwaku` as a `Store client` using the `storenode` option. This
For example, consider a `nwaku` node that does not persist messages but can query peers for historical messages: For example, consider a `nwaku` node that does not persist messages but can query peers for historical messages:
```shell ```shell
./build/wakunode2 --storenode=/dns4/node-01.ac-cn-hongkong-c.wakuv2.prod.statusim.net/tcp/30303/p2p/16Uiu2HAm4v86W3bmT1BiH6oSPzcsSr24iDQpSN5Qa992BCjjwgrD ./build/wakunode2 --storenode=/dns4/node-01.ac-cn-hongkong-c.waku.sandbox.status.im/tcp/30303/p2p/16Uiu2HAmSJvSJphxRdbnigUV5bjRRZFBhTtWFTSyiKaQByCjwmpV
``` ```
## Generate and configure a node key ## Generate and configure a node key
@ -219,7 +219,7 @@ For example, consider a `nwaku` node that requests content filtering of messages
```shell ```shell
./build/wakunode2 \ ./build/wakunode2 \
--filternode=/dns4/node-01.ac-cn-hongkong-c.wakuv2.prod.statusim.net/tcp/30303/p2p/16Uiu2HAm4v86W3bmT1BiH6oSPzcsSr24iDQpSN5Qa992BCjjwgrD \ --filternode=/dns4/node-01.ac-cn-hongkong-c.waku.sandbox.status.im/tcp/30303/p2p/16Uiu2HAmSJvSJphxRdbnigUV5bjRRZFBhTtWFTSyiKaQByCjwmpV \
--filter-timeout=21600 --filter-timeout=21600
``` ```
@ -244,7 +244,7 @@ You can configure `nwaku` as a `Light Push client` using the `lightpushnode` opt
For example, consider a `nwaku` node that requests lightpush of published messages from peers: For example, consider a `nwaku` node that requests lightpush of published messages from peers:
```shell ```shell
./build/wakunode2 --lightpushnode=/dns4/node-01.ac-cn-hongkong-c.wakuv2.prod.statusim.net/tcp/30303/p2p/16Uiu2HAm4v86W3bmT1BiH6oSPzcsSr24iDQpSN5Qa992BCjjwgrD ./build/wakunode2 --lightpushnode=/dns4/node-01.ac-cn-hongkong-c.waku.sandbox.status.im/tcp/30303/p2p/16Uiu2HAmSJvSJphxRdbnigUV5bjRRZFBhTtWFTSyiKaQByCjwmpV
``` ```
## Run nwaku behind a reverse proxy ## Run nwaku behind a reverse proxy

2
docs/guides/nwaku/run-docker.md
View File

@ -41,7 +41,7 @@ Run `nwaku` using the most typical configuration:
```shell ```shell
docker run -i -t -p 60000:60000 -p 9000:9000/udp statusteam/nim-waku:v0.20.0 \ docker run -i -t -p 60000:60000 -p 9000:9000/udp statusteam/nim-waku:v0.20.0 \
--dns-discovery=true \ --dns-discovery=true \
--dns-discovery-url=enrtree://ANEDLO25QVUGJOUTQFRYKWX6P4Z4GKVESBMHML7DZ6YK4LGS5FC5O@prod.wakuv2.nodes.status.im \ --dns-discovery-url=enrtree://AIRVQ5DDA4FFWLRBCHJWUWOO6X6S4ZTZ5B667LQ6AJU6PEYDLRD5O@sandbox.waku.nodes.status.im \
--discv5-discovery=true \ --discv5-discovery=true \
--rpc-address=0.0.0.0 \ --rpc-address=0.0.0.0 \
--nat=extip:[YOUR PUBLIC IP] # or, if you are behind a nat: --nat=any --nat=extip:[YOUR PUBLIC IP] # or, if you are behind a nat: --nat=any