mirror/erigon-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2024-12-22 03:30:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updating README to include running two instances on the same machine. (#3460)

Browse Source 
* Updating README to include running two instances on the same machine.

* Updating formatting
This commit is contained in:
Thomas Jay Rush 2022-02-09 17:11:47 -05:00 committed by GitHub
parent 8466cb1b7b
commit 1e42e0679a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -157,6 +157,27 @@ where `<ip address>` is either localhost or the IP address of the device running
Erigon has been tested with Lighthouse however all other clients that support JSON-RPC should also work.
### Multiple Instances / One Machine
Here's an example of running multiple instances of Erigon against different chains on the same machine:
Against mainnet:
```
./build/bin/erigon --datadir "<your-mainnet-data-path>" --private.api.addr=localhost:9091 -port 30303 --chain mainnet
./build/bin/rpcdaemon --datadir "<your-mainnet-data-path>" --private.api.addr=localhost:9091 --http.api=eth,debug,net,trace,web3,erigon --http.port 8546
```
As usual, use the same `datadir` and `private.api.addr` for both Erigon and RPC. Explicitly specify the chain and the other ports to make things clearer. Quote your path if it has spaces.
Against rinkeby:
```
./build/bin/erigon --datadir "<your-rinkeby-data-path>" --private.api.addr=localhost:9092 -port 30304 --chain rinkeby
./build/bin/rpcdaemon --datadir "<your-rinkeby-data-path>" --private.api.addr=localhost:9092 --http.api=eth,debug,net,trace,web3,erigon --http.port 8547
```
Same command, but use different `datadir` and different ports throughout.
### Dev Chain
<code> 🔬 Detailed explanation is [DEV_CHAIN](/DEV_CHAIN.md).</code>