Jakub Sokołowski
2b566db298
It appears it is being used by Rendezvous, and if that protocol is not being used there is no need to set `AdvertiseAddr` either. I also adjusted all the `Makefile`s to not depend on `PUBLIC_IP` variable. Signed-off-by: Jakub Sokołowski <jakub@status.im> |
||
---|---|---|
.. | ||
Makefile | ||
README.md | ||
docker-compose.yml |
README.md
Status Bootnode
This folder contains setup for running your own Bootnode. It uses:
- Docker Compose for managing the bootnode container.
- Makefile to simplify the process for the user.
Requirements
This Makefile uses two tools: jq
and docker-compose
.
Usage
To simply start a container run make
, other commands include:
make start
- Starts thestatus-go-bootnode
container.make stop
- Stops the container.make show
- Shows you current status of the container.make logs
- Shows you logs of the container.make enode
- Showsenode
address of bootnode.make keys/nodekey
- Creates unique identity for bootnode.
Settings
All settings are passed through environment variables:
LISTEN_PORT
- Bootnode UDP port, by default it's30301
but you might want to use443
.RPC_PORT
- Control port making it possible to use the JSON-RPC API.API_MODULES
- API modules to be made available via theRPC_PORT
.CONTAINER_IMG
- Name of the container image. (default:statusteam/status-go
)CONTAINER_TAG
- Tag of container image to use. (default:v0.64.3
)CONTAINER_NAME
- Name of the container that will be created. (default:status-go-bootnode
)LOG_LEVEL
- Set level of log messages to show. (valid:1=ERROR
,2=WARN
,3=INFO
,4=DEBUG
,5=TRACE
)