Ansible role for a go-ethereum container in Status infra

Go to file

Jakub Sokołowski 4583821179 extend --ws.origins value to be same as rpc Defaulting to `localhost` might be causing issues when `nim-waku` nodes are trying to connect. For some reason there's no clear error like with RPC. Signed-off-by: Jakub Sokołowski <jakub@status.im>		2022-10-17 19:15:23 +02:00
defaults	extend --ws.origins value to be same as rpc	2022-10-17 19:15:23 +02:00
handlers	add tasks, defailts, and handlers for the role	2019-04-26 11:54:14 +02:00
meta	add metadata for role	2019-04-26 11:29:00 +02:00
tasks	jwt: let Geth generate secret by itself	2022-08-16 16:40:33 +02:00
templates	extend --ws.origins value to be same as rpc	2022-10-17 19:15:23 +02:00
LICENSE	add MIT license	2019-04-26 15:31:12 +02:00
README.md	dont set --cache if not specified, it messes with things	2020-11-24 14:46:50 +01:00

Description

This role configures a geth(go-ethereum) container.

The image used by default is ethereum/client-go.

Configuration

The only mandaotry settings is the account password, which can be set to an empty string:

geth_account_password: 'my-secret-password'

Other important settings are:

geth_cont_name: 'geth-mainnet'
geth_network_name: 'mainnet'
geth_sync_mode: 'full'
geth_log_level_name: 'info'
geth_consul_extra_tags: ['mytag']

By default this role creates a new account. If you want to control the account used by the geth process you can use:

geth_account_addr: 0x1j98dsa087fh09as8d7fhsa98dhfas9s0dasjd0d
geth_account_pass: my-secret-account-pass
geth_account_json: '{"account":"json_data"}'

By default we create a Consul service definition, disable it using:

geth_consul_enabled: false

For the rest see the defaults/main.yml config file.

Currently only 3 networks are supported: mainnet, ropsten, goerli, and yolov1.
Setting --cache values higher than 1/3rd of available memory will cause trouble syncing.