0708fcd7cf
The `eth1_monitor` check to require engine API from bellatrix onward has issues in setups where the EL and CL are started simultaneously because the EL may not be ready to answer requests by the time that the check is performed. This can be observed, e.g., on Raspberry Pi 4 when using Besu as the EL client. Now that the merge transition happened, the check is also not that useful anymore, as users have other ways to know that their setup is not working correctly (e.g., repeated exchange logs) |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| CNAME | ||
| README.md | ||
| mkdocs.yml | ||
README.md
The Nimbus Guide is written using markdown and material for mkdocs.
See the Makefile for setup.
The guide is divided into several sections - broadly:
- Guides - walk-throughs that allow the user to get started with a specific area of the client
- How-to:s - short pages that show the user how to solve a specific problem or perform a specific task
- Reference - pages describing how specific parts of Nimbus work, reference-style
- "Other" - explanations of concepts, background etc.
Resources
- material for mkdocs - doc generator
- divio - useful resource diving into the above section structure