-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(book): basic pruning chapter #4334
Conversation
Codecov Report
see 9 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
> TODO: `prune parts / RPC methods` table that shows which RPCs becomes unavailable when certain parts of the data | ||
> are pruned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, we can do in follow-up, but for sure before alpha.8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should basically recommend some use-case driven example configs, for very very aggressive pruners e.g.
Reth also supports pruning of historical data and running as a full node. This chapter will walk through | ||
the steps for running Reth as a full node, what caveats to expect and how to configure your own pruned node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add how big the node is with various configs in followup
As per the PR title.