Skip to content
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.

Sign up for GitHub

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

fix: pruning-at-boot default #200

Merged
merged 5 commits into from
Aug 30, 2023
Merged

fix: pruning-at-boot default #200

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
eca068b
fix: pruning-at-boot default
gfukushima Aug 30, 2023
3d57631
Update docs/how-to/configure-slashing-protection.md
gfukushima Aug 30, 2023
6585789
fix: pruning-at-boot default in the subcommand reference
gfukushima Aug 30, 2023
da413a0
Merge remote-tracking branch 'gfukushima/fix_pruning-at-boot_section'…
gfukushima Aug 30, 2023
290bad8
Update docs/reference/cli/subcommands.md
alexandratran Aug 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/how-to/configure-slashing-protection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,16 +138,16 @@ Enable pruning by setting
[`--slashing-protection-pruning-enabled`](../reference/cli/subcommands.md#slashing-protection-pruning-enabled)
to `true`.

By default, Web3Signer prunes the database on startup, and then after each pruning interval.
You can disable pruning at startup and start pruning after the pruning interval by setting
Web3Signer can prune the database on startup, and then after each pruning interval.
By default, this feature is disabled. You can enable pruning at startup and start pruning after the pruning interval by setting
[`--slashing-protection-pruning-at-boot-enabled`](../reference/cli/subcommands.md#slashing-protection-pruning-at-boot-enabled)
to `false`.
to `true`.

You can include additional optional pruning configuration options.
For example, run:

```bash
web3signer eth2 --slashing-protection-db-url="jdbc:postgresql://localhost/web3signer" --slashing-protection-db-username=postgres --slashing-protection-db-password=password --slashing-protection-pruning-enabled=true --slashing-protection-pruning-at-boot-enabled=false --slashing-protection-pruning-epochs-to-keep=5000 --slashing-protection-pruning-interval=18
web3signer eth2 --slashing-protection-db-url="jdbc:postgresql://localhost/web3signer" --slashing-protection-db-username=postgres --slashing-protection-db-password=password --slashing-protection-pruning-enabled=true --slashing-protection-pruning-at-boot-enabled=true --slashing-protection-pruning-epochs-to-keep=5000 --slashing-protection-pruning-interval=18
```

:::caution Warning
Expand Down