Our Lighthouse docs currently differ from Lighthouse's file structure and defaults.
We should try to stick as close to Lighthouse's defaults, so we can refer the user as much as possible to their documentation. This reduces our long-term documentation lift.
This may require us to review how we structure our overall validator documentation, as we shift towards native client documentation.
Example 1: Different datadir
- Lighthouse Book: defaults to
.lighthouse/gnosis
- Our documentation:
/home/gnosis/consensus
See https://lighthouse-book.sigmaprime.io/validator-management.html
Example 2: Uses validator_definitions.yml to configure
See https://lighthouse-book.sigmaprime.io/validator-management.html
Example 3: Importing validator_keys
- Lighthouse book: imports from
validator_keys directory
- Our documentation: uses different volumes
See https://lighthouse-book.sigmaprime.io/validator-import-launchpad.html
Our Lighthouse docs currently differ from Lighthouse's file structure and defaults.
We should try to stick as close to Lighthouse's defaults, so we can refer the user as much as possible to their documentation. This reduces our long-term documentation lift.
This may require us to review how we structure our overall validator documentation, as we shift towards native client documentation.
Example 1: Different datadir
.lighthouse/gnosis/home/gnosis/consensusSee https://lighthouse-book.sigmaprime.io/validator-management.html
Example 2: Uses
validator_definitions.ymlto configureSee https://lighthouse-book.sigmaprime.io/validator-management.html
Example 3: Importing validator_keys
validator_keysdirectorySee https://lighthouse-book.sigmaprime.io/validator-import-launchpad.html